Claude Skills 实践指南：把 Prompt 封装成可复用的 AI 工作流

release-notes-skill/
├── SKILL.md
├── scripts/
│   └── collect_commits.py
├── references/
│   ├── release-note-style.md
│   └── product-terminology.md
└── assets/
    └── release-note-template.md

---
name: release-notes
description: Generate customer-facing release notes from Git commits, pull request summaries, and product terminology. Use this skill when the user asks to create, rewrite, or standardize release notes, changelogs, or version update announcements.
---

# Release Notes Skill

## Goal

Create concise, customer-facing release notes from technical change records.

## Inputs

The user may provide one or more of the following:

- Git commit list
- Pull request summaries
- Version number
- Product area
- Target audience
- Draft release notes

If required information is missing, ask for it before generating the final release notes.

## Workflow

1. Identify the release scope: version, date range, product area, and audience.
2. Group changes into user-facing categories:
   - New features
   - Improvements
   - Bug fixes
   - Breaking changes
   - Deprecations
3. Remove internal implementation details unless they affect users.
4. Apply the tone and terminology from `references/release-note-style.md`.
5. Use `assets/release-note-template.md` as the final structure.
6. If commit data needs parsing, use `scripts/collect_commits.py`.

## Output Requirements

- Use clear headings.
- Keep each bullet short.
- Explain user impact, not internal code changes.
- Mark breaking changes explicitly.
- Do not invent features that are not present in the input.

description: Helps with writing.

description: Generate customer-facing release notes from Git commits, pull request summaries, and product terminology. Use this skill when the user asks to create, rewrite, or standardize release notes, changelogs, or version update announcements.

invoice-review/
├── SKILL.md
├── scripts/
│   ├── validate_amount.py
│   └── normalize_invoice_fields.py
├── references/
│   ├── reimbursement-policy.md
│   └── expense-categories.md
└── assets/
    └── review-result-template.md

帮我看一下这个 PR 有没有问题
检查这段代码是否符合团队规范
review 一下这个 diff
这个提交有没有潜在 bug

description: Review code changes, pull request diffs, or patches for correctness, maintainability, security risks, and team coding standards. Use this skill when the user asks for code review, PR review, diff analysis, or patch inspection.

code-review/
├── SKILL.md
└── references/
    ├── backend-style-guide.md
    ├── security-checklist.md
    ├── database-guidelines.md
    └── api-design-rules.md

When reviewing backend code, consult `references/backend-style-guide.md`.

When the change involves authentication, authorization, input validation, file upload, SQL queries, secrets, or external dependencies, also consult `references/security-checklist.md`.

When the change modifies database schema, query logic, indexes, or transactions, consult `references/database-guidelines.md`.

# scripts/collect_commits.py
import subprocess
import sys

def collect_commits(start_ref: str, end_ref: str) -> str:
    result = subprocess.run(
        ["git", "log", "--oneline", f"{start_ref}..{end_ref}"],
        capture_output=True,
        text=True,
        check=True,
    )
    return result.stdout.strip()

if __name__ == "__main__":
    if len(sys.argv) != 3:
        raise SystemExit("Usage: python collect_commits.py <start_ref> <end_ref>")

    print(collect_commits(sys.argv[1], sys.argv[2]))

<!-- assets/release-note-template.md -->

# Version {{version}}

Release date: {{date}}

## New Features

- ...

## Improvements

- ...

## Bug Fixes

- ...

## Breaking Changes

- ...

## Deprecations

- ...

## Migration Notes

- ...

Use `assets/release-note-template.md` as the final output structure.
If a section has no relevant changes, omit that section unless it is "Breaking Changes".
Always include "Breaking Changes"; write "None" if there are no breaking changes.

## Trigger Tests

- [ ] 用户说“生成 changelog”时触发
- [ ] 用户说“写版本更新公告”时触发
- [ ] 用户只问“解释这段代码”时不触发
- [ ] 用户要求“写营销邮件”时不触发

## Execution Tests

- [ ] 缺少版本号时会追问
- [ ] 不会编造不存在的功能
- [ ] 会把内部重构从用户可见更新中剔除
- [ ] Breaking Changes 永远单独列出
- [ ] 输出符合模板

skills/
├── code-review/
├── release-notes/
├── incident-analysis/
├── api-doc-generation/
└── sql-query-check/

description: Helps analyze data.

description: Analyze CSV sales reports to identify revenue trends, regional performance changes, and abnormal drops. Use this skill when the user uploads sales CSV files or asks for sales trend analysis.

If required inputs are missing, ask for them before producing the final output.

If an external tool fails, report:
1. which tool failed;
2. what input was used;
3. what error was returned;
4. what the user can do next.

Do not silently continue with guessed data.

---
name: your-skill-name
description: Describe the exact task, expected inputs, and user intents that should trigger this skill. Keep the scope narrow and concrete.
---

# Skill Name

## Goal

State what this skill helps Claude accomplish.

## When to Use

Use this skill when:
- ...
- ...

Do not use this skill when:
- ...
- ...

## Inputs

Expected inputs:
- ...

If required inputs are missing, ask the user for clarification before producing the final answer.

## Workflow

1. ...
2. ...
3. ...

## References

Use these files when relevant:
- `references/example.md`: ...

## Scripts

Use these scripts when deterministic processing is needed:
- `scripts/example.py`: ...

## Output Format

Follow this structure:
- ...

## Quality Checks

Before finalizing, verify:
- ...
- ...
- ...

your-skill-name/
├── SKILL.md
├── scripts/
├── references/
└── assets/