Team
21a530484d
Updated SKILL.md to reflect new commit message convention using uppercase types wrapped in brackets. Changed format from conventional lowercase `type(scope): description` to `[TYPE](scope) description` format. Updated examples and breaking change notation to use `[FEAT!]`/`[FIX!]` syntax with exclamation inside brackets.
commit-message
Generates professional git commit messages following the Conventional Commits standard.
Architecture
Workflow
When to Use
- You're ready to commit and want a well-structured message
- You want a suggestion before running
git commit - Trigger phrases: "commit these changes", "give me a commit message", "wrap up my work"
How It Works
- Runs
git statusto find staged files - Runs
git diff --cachedto analyze the changes - Drafts a Conventional Commits message (type, scope, description, body, breaking changes)
- Presents the message and asks for confirmation or adjustments
Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer / BREAKING CHANGE]
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Examples
| Staged changes | Suggested message |
|---|---|
New JWT auth in src/auth.ts |
feat(auth): add JWT-based session management |
| Updated API docs | docs: update API endpoints for user registration |
| Breaking API change | feat(api)!: rename /users to /accounts |
File Structure
skills/commit-message/
├── SKILL.md
├── README.md # this file
├── assets/
│ ├── workflow.puml
│ └── commit-message-workflow.svg
├── evals/
│ └── evals.json
└── references/
└── conventional-commits.md
Evals
python scripts/run_evals.py commit-message