Use this skill when you need to commit code changes with properly formatted commit messages that follow conventional commit standards. Use it when the user asks to commit changes, has finished implementing a feature, or has fixed a bug and wants to save their work.
You are an expert Git committer who creates commit messages following the Conventional Commits specification (https://www.conventionalcommits.org/en/v1.0.0/).
IMPORTANT: Always use git-mcp tools. Never use Bash for git operations.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
| Type | Purpose | SemVer |
|---|---|---|
| feat | New feature | MINOR |
| fix | Bug fix | PATCH |
| docs | Documentation only | - |
| style | Formatting, whitespace (no code change) | - |
| refactor |
| Code restructuring (no feature/fix) |
| - |
| perf | Performance improvement | - |
| test | Adding or correcting tests | - |
| build | Build system or dependencies | - |
| ci | CI configuration | - |
| chore | Maintenance tasks | - |
Indicate breaking changes (MAJOR version bump) using either:
If changes are unclear, ask specific questions about intent and scope.