Help users write professional git commit messages following Conventional Commits. Use when users ask about commits, need help writing commit messages, want to validate commit format, ask about git message conventions, or use slash commands like /commit, /validate, /changelog, /version.
View on GitHubFebruary 1, 2026
Select agents to install to:
npx add-skill https://github.com/AnthemFlynn/ccmp/blob/main/plugins/git-commit/skills/git-commit/SKILL.md -a claude-code --skill git-commitInstallation paths:
.claude/skills/git-commit/# Git Commit Assistant Help users write clear, professional commit messages following the Conventional Commits specification. ## Slash Commands Recognize and respond to these slash commands: - `/commit` - Smart commit helper (auto-analyzes code if staged, otherwise interactive) - `/validate <message>` - Validate a commit message format - `/types` - Show all commit types with descriptions - `/scopes` - Explain scopes and show examples - `/breaking` - Guide for creating breaking change commits - `/changelog` - Generate changelog from recent commits - `/version` - Determine next semantic version from commits - `/examples` - Show comprehensive commit examples - `/fix` - Help amend/fix the last commit When user types a slash command, execute that specific workflow. ## User Intent Recognition When users ask questions like: - "Help me write a commit for..." → Use smart analysis if code is staged - "Help me commit" (no details) → Check for staged changes, analyze if found, otherwise ask - "How should I commit this?" → Smart analysis mode - "Is this commit message good?" → Validation mode - "What's the right format for..." → Show format and examples Guide them naturally through creating a proper commit. ## Commit Format Standard format: ``` <type>(<scope>): <description> <body> <footer> ``` **Types:** - `feat` - New feature - `fix` - Bug fix - `refactor` - Code change without behavior change - `perf` - Performance improvement - `style` - Formatting, whitespace - `test` - Test changes - `docs` - Documentation - `build` - Build/dependencies - `ops` - Infrastructure/deployment - `chore` - Maintenance **Scope:** Optional context (e.g., `api`, `auth`, `database`) **Description:** Short summary, lowercase, imperative mood, no period, under 100 chars **Body:** Optional explanation of what and why **Footer:** Optional issue references (`Closes #123`) or breaking changes ## Breaking Changes Add `!` before colon: `feat(api)!: remove endpoint` Include in footer: `