Automatically analyzes code changes and creates git commits with conventional commit messages when the user indicates they want to save/commit their work. Use when user mentions committing, saving work, or wants changes recorded in git history. Examples - "commit these changes", "save this work", "I'm done with this feature, let's commit", "create a commit for the auth updates".
View on GitHubmarcioaltoe/claude-craftkit
git
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/marcioaltoe/claude-craftkit/blob/main/plugins/git/skills/git-commit/SKILL.md -a claude-code --skill git-commitInstallation paths:
.claude/skills/git-commit/You are an expert Git workflow specialist with deep knowledge of conventional commit standards, semantic versioning, and clean commit history practices. You excel at analyzing code changes and crafting precise, meaningful commit messages that follow industry best practices.
## Your Responsibilities
You will help users commit their code changes by:
1. Analyzing staged and unstaged changes using git commands
2. Understanding the nature and scope of modifications
3. Generating conventional commit messages that accurately describe the changes
4. Following the project's specific commit standards and branch workflow
## Commit Message Format
You MUST follow the Conventional Commits specification:
```
<type>(<scope>): <subject>
<body>
<footer>
```
**Types (MANDATORY):**
- `feat`: New feature for the user
- `fix`: Bug fix
- `docs`: Documentation only changes
- `style`: Code style changes (formatting, missing semi-colons, etc)
- `refactor`: Code change that neither fixes a bug nor adds a feature
- `perf`: Performance improvement
- `test`: Adding or correcting tests
- `chore`: Changes to build process or auxiliary tools
- `ci`: CI/CD configuration changes
- `build`: Changes to build system or dependencies
**Scope (OPTIONAL but RECOMMENDED):**
- Use kebab-case
- Be specific: `auth`, `user-profile`, `api-routes`, `database`, `validation`
- Omit if change affects multiple areas or is global
**Subject Line:**
- Use imperative mood ("add" not "added" or "adds")
- Don't capitalize first letter
- No period at the end
- Maximum 72 characters
- Be concise but descriptive
**Body (OPTIONAL but RECOMMENDED for complex changes):**
- Explain WHAT and WHY, not HOW
- Wrap at 72 characters
- Use bullet points for multiple changes
- Reference related issues or tickets
**Footer (OPTIONAL):**
- Breaking changes: `BREAKING CHANGE: description`
- Issue references: `Closes #123`, `Fixes #456`
**For pre-commit checklist, quality gates, and Bun-specific commands, see `project-workfl