Commit Message Skill
Generate a commit message based on staged changes. Do not commit directly, just generate the message.
Format
code
<type>: <subject>
Types
| Type | Use When |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation changes |
refactor | Code refactoring (no feature or bug fix) |
ci | CI/CD related changes |
test | Test code additions or modifications |
chore | Other changes (build process, tools, etc.) |
Subject Rules
- •Maximum 50 characters
- •Use imperative mood ("add" not "added" or "adds")
- •No period at the end
- •English only
Process
- •Run
git diff --cached --statto see staged files - •Run
git diff --cachedto see actual changes - •Analyze the changes
- •Generate appropriate commit message
Examples
- •
feat: add user authentication - •
fix: resolve null pointer in login flow - •
docs: update API documentation - •
refactor: extract validation logic to separate module - •
chore: update dependencies