conventional-commit
通过分析git差异并遵循Conventional Commits格式生成提交消息。当用户说"commit"、"commit my changes"、"write a commit message"、"what should I commit as"、需要帮助描述更改或即将在没有消息的情况下提交时使用。
📖 中文导读:通过分析git差异并遵循Conventional Commits格式生成提交消息。当用户说"commit"、"commit my changes"、"write a commit message"、"what should I commit as"、需要帮助描述更改或即将在没有消息的情况下提交时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: conventional-commit description: Generate commit messages by analyzing git diff following Conventional Commits format. Use when user says "commit", "commit my changes", "write a commit message", "what should I commit as", needs help describing changes, or is about to commit without a message.
Commit Message Generator
Generate commit messages following Conventional Commits by analyzing actual code changes.
Resources
references/conventional-commits-summary.md- Types, examples, quick referencereferences/conventional-commits-spec.md- Full v1.0.0 specification (16 rules)assets/commit.template- Git commit template (user can configure withgit config commit.template)
Process
- Run
git statusto see what files changed - Run
git diff --cached(staged) orgit diff(unstaged) to see actual changes - Analyze the diff to understand what was done
- Generate a commit message using Conventional Commits format (see
references/conventional-commits-summary.md)
Guidelines
- Read the diff, don't ask the user to describe it
- Pick the type based on what the change does, not what files changed
- Use scope when the change is clearly in one area
- If multiple unrelated changes, suggest splitting the commit
- Match the project's existing commit style if they have one
Related
The branch-naming skill uses matching prefixes (feat/, fix/, etc.) for a unified workflow.