Codex Skills 怎麼寫自己的工作流：從重複提示詞到可複用 SKILL.md

1
2
3
4
5

把站內中文文章改寫成可發布版本
把某類日誌整理成日報
把 PR review 固定成安全、測試、回歸三段
把部署流程固定成 build、sync、purge、submit
把產品圖片處理成統一規格

1
2

my-workflow/
  SKILL.md

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

my-workflow/
  SKILL.md
  references/
    checklist.md
    examples.md
  scripts/
    validate.ps1
    collect-data.py
  assets/
    report-template.md

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

---
name: my-workflow
description: Use when the user asks to <具體任務觸發條件>. Handles <輸入>, produces <輸出>, and verifies <完成標準>.
---

# My Workflow

## Purpose

說明這個 skill 解決什麼重複任務，不解決什麼。

## When To Use

- 使用者明確提到某個關鍵詞時使用。
- 任務需要固定步驟、固定輸出或固定校驗時使用。
- 如果只是普通問答，不使用。

## Inputs

- 需要使用者提供什麼。
- 可以從倉庫裡自動發現什麼。
- 缺少資訊時應如何假設或提問。

## Workflow

1. 檢查當前狀態。
2. 讀取必要文件。
3. 執行核心處理。
4. 執行輕量驗證。
5. 回報結果和未完成事項。

## Constraints

- 不要改哪些文件。
- 不要執行哪些命令。
- 哪些欄位必須保留。
- 遇到衝突怎麼處理。

## Verification

- 檢查輸出文件是否存在。
- 檢查格式是否有效。
- 檢查命令是否通過。
- 檢查是否有殘留風險。

## Reporting

最終回覆需要包含：

- 改了什麼。
- 沒改什麼。
- 驗證結果。
- 需要使用者注意的風險。

1

description: Help with reports.

1

description: Use when the user asks to turn Git commits, issue updates, or daily work notes into a weekly engineering report with sections for completed work, risks, blockers, and next actions.

1

你是一位資深工程師，請幫我檢查這次改動有沒有問題，重點關注邊界條件和測試。

1
2
3
4
5
6
7

## Workflow

1. 先執行 `git status --short`，確認改動範圍。
2. 讀取 diff，而不是只看文件名。
3. 按嚴重程度列出 findings。
4. 優先找 bug、回歸風險、安全問題和缺失測試。
5. 如果沒有問題，明確說明未發現高置信問題，並列出剩餘風險。

1
2
3
4
5

## References

- 需要判斷報告品質時，讀取 `references/report-rubric.md`。
- 需要生成完整模板時，讀取 `assets/weekly-report-template.md`。
- 普通摘要任務不要讀取完整示例庫。

1
2
3
4
5
6

weekly-report/
  SKILL.md
  assets/
    weekly-report-template.md
  scripts/
    collect-git-summary.ps1

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

---
name: weekly-report
description: Use when the user asks to create a weekly work report from Git commits, notes, issue updates, or chat summaries. Produces a concise Chinese report with completed work, impact, blockers, and next week plan.
---

# Weekly Report

## Workflow

1. Confirm the report date range. If missing, use the current week.
2. Collect source material from user-provided notes first.
3. If the user asks to include Git work, run `scripts/collect-git-summary.ps1`.
4. Group work by project or theme, not by raw commit order.
5. Produce a concise Chinese report using `assets/weekly-report-template.md`.
6. Mark uncertain items as uncertain instead of inventing progress.

## Constraints

- Do not expose private commit hashes unless the user asks.
- Do not claim shipped work if the source only shows drafts or experiments.
- Keep blockers separate from completed work.

## Reporting

Return the report content and list which sources were used.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21

---
name: focused-code-review
description: Use when the user asks for a code review of the current working tree, a commit, or a pull request. Prioritize bugs, regressions, security risks, and missing tests; do not rewrite code unless asked.
---

# Focused Code Review

## Workflow

1. Inspect `git status --short`.
2. Read the relevant diff.
3. Identify behavior changes before style issues.
4. List findings first, ordered by severity.
5. Include file and line references when possible.
6. If no issues are found, say so directly and mention remaining test gaps.

## Constraints

- Do not make code edits during review.
- Do not focus on formatting unless it can cause a real bug.
- Do not summarize before findings.

1

$weekly-report 根據這週提交生成一版週報

1

幫我根據這週 git 提交寫一版週報