auto-commit
Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook.
When & Why to Use This Skill
The Auto-Commit Claude skill streamlines the software development lifecycle by automating the Git commit process according to the Conventional Commits specification. It intelligently analyzes code changes to determine the appropriate commit type—such as feat, fix, docs, or refactor—and generates standardized, professional commit messages. By automating staging and committing, it ensures a clean, searchable, and maintainable version control history while reducing the manual overhead for developers.
Use Cases
- Standardizing Team Workflows: Enforce the Conventional Commits standard across a project automatically, ensuring all contributors maintain a consistent and professional Git log.
- Accelerating Feature Deployment: Automatically generate 'feat:' commits with optional scopes after implementing new functionality, keeping the development timeline organized.
- Efficient Bug Resolution: Create precise 'fix:' commits immediately after resolving issues, improving traceability and making it easier to generate automated changelogs.
- Documentation Maintenance: Simplify the process of updating READMEs and technical guides by automatically applying the 'docs:' prefix to documentation-only changes.
- Codebase Refactoring and Cleanup: Effortlessly categorize 'refactor:', 'style:', or 'chore:' commits during routine maintenance or dependency updates to keep the project history meaningful.
| name | auto-commit |
|---|---|
| description | Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook. |
Auto-Commit with Conventional Commits
Automatically stage and commit changes using the conventional commits specification.
Conventional Commits Format
<type>(<scope>): <description>
[optional body]
Commit Types
| Type | When to Use |
|---|---|
feat |
New feature or functionality |
fix |
Bug fix |
docs |
Documentation only changes |
chore |
Maintenance (deps, configs, build) |
refactor |
Code restructuring without behavior change |
test |
Adding or modifying tests |
style |
Formatting, whitespace, linting |
perf |
Performance improvements |
ci |
CI/CD changes |
Scope (Optional)
Add scope in parentheses for context:
feat(auth): add login endpointfix(api): handle null responsedocs(readme): update install instructions
Commit Workflow
- Check for changes:
git status - If changes exist:
- Stage all:
git add -A - Review staged:
git diff --staged - Determine type from changes
- Write concise description (imperative mood)
- Commit with proper format
- Stage all:
Message Guidelines
- Use imperative mood: "add feature" not "added feature"
- Keep first line under 72 characters
- Don't end with period
- Be specific but concise
Good Examples
feat(api): add user authentication endpoint
fix: resolve null pointer in payment processing
docs: update API usage examples
chore: upgrade dependencies to latest versions
refactor(db): extract query builder to separate module
Bad Examples
updated stuff # Too vague
Fixed the bug. # Don't end with period
Added new feature # Wrong tense
Important
- Only commit, do NOT push
- Always use conventional commits format
- Include scope when it adds clarity