Git Commit Guidelines
This skill provides guidance for writing conventional commit messages.
Commit Message Format
code
<type>(<scope>): <subject> <body> <footer>
Types
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, no code change |
| refactor | Code change, no feature/fix |
| test | Adding tests |
| chore | Maintenance tasks |
Rules
- •Subject line max 50 characters
- •Use imperative mood ("Add feature" not "Added feature")
- •No period at end of subject
- •Blank line between subject and body
- •Body explains what and why, not how
Examples
Good:
code
feat(auth): add OAuth2 login support Implement Google and GitHub OAuth providers. Closes #123
Bad:
code
Updated the login page to support OAuth
Quick Reference
- •
feat: New functionality for users - •
fix: Bug fix for users - •
docs: Documentation changes - •
refactor: Code restructuring - •
test: Test additions/changes - •
chore: Build, CI, dependencies