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
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21

---
name: blog-post-publish
description: Use when the user asks to create or update a Hugo blog post in this repository. Handles post numbering, front matter, Markdown structure, lightweight validation, and publish-ready reporting.
---

# Blog Post Publish

## Workflow

1. Check `git status --short`.
2. If creating a new post, find the next numeric directory.
3. Create only the requested language file.
4. Preserve slug and date for existing posts.
5. Validate front matter, code fences, links, and encoding.
6. Do not run a full Hugo build unless requested.

## Constraints

- Do not overwrite the active article when the user asks for a new post.
- Do not generate translations unless the user explicitly asks.
- Do not change published URL fields casually.

1

$weekly-report 根据这周提交生成一版周报

1

帮我根据这周 git 提交写一版周报