auto-commit

James1218's avatarfrom James1218

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.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 30, 2025
[Developer Tools]

When & Why to Use This Skill

This Claude skill automates the Git commit process by strictly adhering to the Conventional Commits specification. It streamlines the developer workflow by automatically staging changes and generating standardized, professional commit messages—such as feat, fix, and docs—ensuring a clean, readable, and searchable project history that facilitates better collaboration and automated changelog generation.

Use Cases

  • Automated Bug Tracking: Automatically generate 'fix' type commits immediately after resolving code issues to maintain a precise record of bug fixes.
  • Feature Implementation: Seamlessly commit new functionalities using the 'feat' prefix, ensuring every new capability is documented in the version history without manual overhead.
  • Documentation Maintenance: Effortlessly categorize README or wiki updates under 'docs' commits, keeping the repository's meta-information organized and professional.
  • Workflow Standardization: Enforce consistent commit message formats across a project, making it easier for teams to review history, perform audits, and automate release notes.
  • Refactoring and Maintenance: Automatically handle 'refactor' or 'chore' commits during code restructuring or dependency updates to keep the main development branch clean.
nameauto-commit
descriptionAutomatically 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 endpoint
  • fix(api): handle null response
  • docs(readme): update install instructions

Commit Workflow

  1. Check for changes: git status
  2. 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

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