Agent skill
conventional-commits
Conventional Commits standard for structured commit messages - types, scopes, breaking changes, and changelog generation. Auto-triggers during git operations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/conventional-commits-bigdegenenergy-ai-dev-toolkit
SKILL.md
Conventional Commits Skill
Commit Message Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Examples
feat(auth): add OAuth2 login with Google provider
fix(api): prevent null pointer on missing user profile
docs: update API endpoint documentation
refactor(db): extract connection pooling into shared module
test(payments): add integration tests for Stripe webhook
chore(deps): bump fastapi from 0.114 to 0.115
feat!: drop support for Python 3.9
Commit Types
| Type | When to Use | Bumps |
|---|---|---|
feat |
New feature or capability | MINOR |
fix |
Bug fix | PATCH |
docs |
Documentation only | - |
style |
Formatting, whitespace (no logic change) | - |
refactor |
Code restructuring (no behavior change) | - |
perf |
Performance improvement | PATCH |
test |
Adding or fixing tests | - |
build |
Build system or dependencies | - |
ci |
CI/CD configuration | - |
chore |
Maintenance tasks | - |
revert |
Reverting a previous commit | PATCH |
Scopes
Scopes are project-specific. Common patterns:
# By module/component
feat(auth): ...
fix(api): ...
refactor(db): ...
# By domain
feat(payments): ...
fix(notifications): ...
# By layer
feat(ui): ...
fix(middleware): ...
Breaking Changes
Mark breaking changes with ! after type/scope OR with a BREAKING CHANGE: footer:
# With ! marker
feat!: change API response format to JSON:API
# With footer
feat(api): change authentication to bearer tokens
BREAKING CHANGE: API now requires Bearer token in Authorization
header instead of API key in query parameter.
Description Rules
- Use imperative mood: "add" not "added" or "adds"
- Don't capitalize first letter
- No period at end
- Under 72 characters
- Explain WHAT, not HOW (the diff shows how)
# GOOD
feat(auth): add password reset via email
fix(parser): handle empty input without crashing
refactor(db): replace raw SQL with parameterized queries
# BAD
feat(auth): Added a password reset feature. # past tense, period, capitalized
fix: fixed the bug # vague, past tense
refactor: code cleanup # too vague
Body and Footers
fix(api): handle race condition in concurrent order creation
The previous implementation allowed duplicate orders when two
requests arrived simultaneously. Added a database-level unique
constraint on (user_id, idempotency_key) and retry logic.
Fixes: #234
Reviewed-by: @teammate
Common Footers
| Footer | Purpose |
|---|---|
Fixes: #123 |
Closes a GitHub issue |
Refs: #456 |
References without closing |
BREAKING CHANGE: ... |
Breaking change description |
Reviewed-by: @user |
Code reviewer |
Co-authored-by: Name <email> |
Co-author attribution |
Multi-Line Commit (Bash)
git commit -m "$(cat <<'EOF'
feat(auth): add OAuth2 login with Google provider
Implements the full OAuth2 authorization code flow:
- Redirect to Google consent screen
- Handle callback with auth code exchange
- Create/link user account on first login
Fixes: #89
EOF
)"
Decision Guide
Did you add a new feature? → feat
Did you fix a bug? → fix
Did you change docs only? → docs
Did you restructure without behavior change? → refactor
Did you improve performance? → perf
Did you add/fix tests only? → test
Did you change CI/CD config? → ci
Did you change build/deps? → build
Does it break backward compatibility? → add ! or BREAKING CHANGE footer
Changelog Generation
Conventional commits enable automatic changelog generation:
# With standard-version (Node.js)
npx standard-version
# With commitizen (Python)
cz changelog
# Manual approach
git log --oneline --format="%s" v1.0.0..HEAD | grep -E "^(feat|fix)"
Generated Changelog Example
## [1.2.0] - 2026-02-12
### Features
- **auth**: add OAuth2 login with Google provider (#89)
- **api**: add batch processing endpoint (#92)
### Bug Fixes
- **api**: prevent null pointer on missing user profile (#91)
- **parser**: handle empty input without crashing (#90)
### BREAKING CHANGES
- **api**: change authentication to bearer tokens
Activation Triggers
This skill auto-activates when prompts contain:
- "commit message", "conventional commit"
- "commit type", "commit scope"
- "breaking change", "changelog"
- "feat:", "fix:", "refactor:"
Integration
- git-workflows skill: Advanced git operations
- cicd-automation skill: Automated releases from commits
- /ship command: Commit, push, and PR
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?