菜单
Write precise Conventional Commits messages from the actual staged diff. Use whenever committing code or asked to write/fix a commit message.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | conventional-commits |
| description | Write precise Conventional Commits messages from the actual staged diff. Use whenever committing code or asked to write/fix a commit message. |
| version | 1.0.0 |
| license | MIT |
| keywords | ["git","commits","conventional-commits","changelog","workflow"] |
Write the message from the diff, not from the conversation. The reader is a
stranger running git log in two years.
git diff --cached --stat then the diff itself.feat new user-visible capability · fix corrects wrong behaviorrefactor no behavior change · perf faster, same behaviordocs · test · build · ci · chore (only when nothing else fits)feat(parser): …. Omit if
the repo doesn't use scopes (check git log --oneline -20 and match style).BREAKING CHANGE: <what breaks and the migration>,
and add ! after the type: feat(api)!: ….git add -p).fix(ingest): treat mtime regressions as edits, not new files
Restored backups can move mtime backwards; we indexed those as fresh
documents, duplicating every chunk. Key on inode+path instead.
Make the agent improve with every task — review the run, distill lessons into durable memory, and reinforce what worked. Use at the end of any non-trivial task, or when the user asks the agent to "learn from this".
Write a blameless, actionable incident postmortem from the raw facts. Use after an outage/incident, or when asked to write up "what happened" for the team.
Write a reviewer-first pull-request description from the actual branch diff. Use when opening a PR or asked to write/improve a PR description.
Root-cause a bug with a hypothesis-driven loop instead of shotgun edits. Use when a bug isn't obvious after the first look, or when asked to "find out why" something fails.
Write tests that catch real regressions — behavior-focused, minimal mocking, edge cases chosen from the code's actual branches. Use when adding tests for new code or backfilling tests for a fix.
Generate or update a CHANGELOG.md in Keep a Changelog format from real git history. Use when cutting a release, tagging a version, or asked "what changed since…".