From latestaiagents
Use this skill when writing Git commit messages. Activate when the user asks about commit message format, conventional commits, how to write good commit messages, commit message best practices, or when they're about to commit changes and need help crafting the message.
npx claudepluginhub latestaiagents/agent-skills --plugin skills-authoringThis skill uses the workspace's default tool permissions.
Write clear, consistent, and meaningful commit messages.
Generates Git commit messages following Conventional Commits spec with types like feat/fix/refactor, scopes, subject/body/footer guidelines, and issue references. Activates on commit requests or git mentions.
Generates concise conventional git commit messages prioritizing 'why' over 'what', with proper types, scopes, imperative mood, and atomic structure. Use when writing commits or learning best practices.
Generates one-shot Conventional Commits messages for staged git changes: feat/fix/refactor types, imperative ≤50 char subjects, optional scopes and Why explanations.
Share bugs, ideas, or general feedback.
Write clear, consistent, and meaningful commit messages.
<type>(<scope>): <subject>
<body>
<footer>
| Type | When to Use |
|---|---|
feat | New feature for the user |
fix | Bug fix for the user |
docs | Documentation only changes |
style | Formatting, missing semicolons, etc. (no code change) |
refactor | Code change that neither fixes a bug nor adds a feature |
perf | Performance improvement |
test | Adding or fixing tests |
chore | Maintenance tasks, dependencies, build changes |
ci | CI/CD configuration changes |
revert | Reverting a previous commit |
The part of the codebase affected:
auth, api, ui, db, config, deps, etc.feat(auth): add password reset functionality
fix(api): handle null response from payment gateway
The payment gateway occasionally returns null instead of an error
object when the service is degraded. This caused uncaught exceptions
in the checkout flow.
Fixes #1234
feat(api)!: change user endpoint response format
BREAKING CHANGE: The /api/users endpoint now returns paginated
results. Clients must update to handle the new response structure:
{ data: [], meta: { page, total } }
refactor(utils): extract date formatting into separate module
Moved date formatting logic from multiple components into a
centralized dateUtils module for better maintainability.
feat(dashboard): redesign analytics widgets
- Add new chart component for user growth
- Implement date range picker
- Add export to CSV functionality
- Update color scheme to match brand guidelines
Co-authored-by: Jane Doe <jane@example.com>
# See what's staged
git diff --staged
# See files changed
git diff --staged --name-only
Ask: What is the PRIMARY purpose of these changes?
featfixrefactorLook at the files changed. What's the common area?
/src/auth/? → scope is authComplete this sentence with your changes: "If applied, this commit will _______________"
Good: "add user avatar upload" Bad: "added user avatar upload functionality to the system"
Include body when:
Fixes #123
Closes #456
BREAKING CHANGE: description
Co-authored-by: Name <email>
feat(<scope>): <what you added>
<why you added it, if not obvious>
Relates to #<issue>
fix(<scope>): <what you fixed>
<what was broken and why>
Fixes #<issue>
chore(deps): update <package> to <version>
<any breaking changes or notes>
Consider documenting your team's conventions:
## Commit Message Convention
- Use conventional commits format
- Scope is required for features and fixes
- Reference issue numbers in footer
- Breaking changes must include BREAKING CHANGE footer
# Set up commit template
git config --global commit.template ~/.gitmessage
# Use commitizen for interactive commits
npx cz
# Validate commits with commitlint
npm install -D @commitlint/{cli,config-conventional}