latestaiagents/commit-message-crafter
skills/developer/git-mastery/commit-message-crafter/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add latestaiagents/agent-skills commit-message-crafterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 2:54 AM13.3s1 file scanned
SKILL.md
- name:
- commit-message-crafter
- description:
- |
Commit Message Crafter
Write clear, consistent, and meaningful commit messages.
When to Use
- Writing a commit message for staged changes
- Following conventional commits format
- Standardizing commit messages across a team
- Writing messages for squash commits or PRs
The Conventional Commits Format
<type>(<scope>): <subject>
<body>
<footer>
Types
| 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 |
Scope (Optional)
The part of the codebase affected:
auth,api,ui,db,config,deps, etc.
Subject Rules
- Use imperative mood: "Add feature" not "Added feature"
- Don't capitalize first letter
- No period at the end
- Max 50 characters (72 absolute max)
- Complete the sentence: "This commit will..."
Examples
Simple Feature
feat(auth): add password reset functionality
Bug Fix with Body
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
Breaking Change
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 } }
Refactoring
refactor(utils): extract date formatting into separate module
Moved date formatting logic from multiple components into a
centralized dateUtils module for better maintainability.
Multiple Changes (Squash Commit)
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 <[email protected]>
Workflow
Step 1: Analyze Changes
# See what's staged
git diff --staged
# See files changed
git diff --staged --name-only
Step 2: Determine Type
Ask: What is the PRIMARY purpose of these changes?
- Adding something new? →
feat - Fixing broken behavior? →
fix - Improving without changing behavior? →
refactor
Step 3: Identify Scope
Look at the files changed. What's the common area?
- All in
/src/auth/? → scope isauth - Mixed areas? → omit scope or use broader term
Step 4: Write Subject
Complete this sentence with your changes: "If applied, this commit will _______________"
Good: "add user avatar upload" Bad: "added user avatar upload functionality to the system"
Step 5: Add Body (If Needed)
Include body when:
- The "why" isn't obvious from the subject
- There are multiple related changes
- Breaking changes need explanation
- Linking to issues/tickets
Step 6: Add Footer (If Needed)
Fixes #123
Closes #456
BREAKING CHANGE: description
Co-authored-by: Name <email>
Quick Templates
Feature
feat(<scope>): <what you added>
<why you added it, if not obvious>
Relates to #<issue>
Bug Fix
fix(<scope>): <what you fixed>
<what was broken and why>
Fixes #<issue>
Dependency Update
chore(deps): update <package> to <version>
<any breaking changes or notes>
Common Mistakes to Avoid
- Vague messages: "fix bug", "update code", "changes"
- Too long: Keep subject under 50 chars
- Wrong tense: "Added" instead of "Add"
- Multiple unrelated changes: Split into separate commits
- No context: Just "fix" without explaining what or why
Team Conventions
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
Tools
# 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}
Related Skills
latestaiagents/skill-testing
development
VerifiedTrustedCommunity
Test skills for correct activation, content quality, and regression — both automated checks (frontmatter validity, lint) and manual verification (query-suite activation testing). Covers CI integration and how to catch skill regressions before users do. Use this skill when adding skills to a repo, setting up CI for a skill library, or debugging "the skill exists but doesn't work". Activate when: test skills, validate skills, skill CI, skill linting, skill activation test, skill regression.
2SKILL.mdUpdated Apr 23, 2026
latestaiagents/skill-frontmatter
documentation
VerifiedTrustedCommunity
Write the YAML frontmatter for a SKILL.md file so it activates reliably — name, description, and activation keywords that the model matches against. Covers length, tone, and the most common frontmatter mistakes. Use this skill when authoring a new skill, fixing a skill that isn't auto-activating, or reviewing skills for publication. Activate when: SKILL.md frontmatter, skill description, skill activation, skill YAML, write a skill, author a skill.
2SKILL.mdUpdated Apr 23, 2026
latestaiagents/skill-activation-patterns
development
VerifiedTrustedCommunity
Design skills that fire at the right moment — neither over-eager (noise) nor under-eager (silent). Covers activation specificity, trigger phrases, disambiguation between overlapping skills, and debugging activation. Use this skill when multiple skills could fire on the same query, a skill never fires, or a skill fires too often. Activate when: skill won't activate, skill over-activates, overlapping skills, skill triggers, skill selection, skill disambiguation.
2SKILL.mdUpdated Apr 23, 2026
latestaiagents/progressive-disclosure
development
VerifiedTrustedCommunity
Structure SKILL.md content so the model reads just enough — concise summary up front, progressively deeper detail, examples on demand. Covers section ordering, length budgets, when to split into multiple skills. Use this skill when writing or refactoring a skill body, one skill has grown too long, or a skill is wordy but not useful. Activate when: SKILL.md structure, skill content, skill too long, split skill, progressive disclosure, skill body.
2SKILL.mdUpdated Apr 23, 2026