Commit Workflow

What problem does it solve?

Inconsistent commit practices lead to messy history, difficult debugging, and poor collaboration. This Skill enforces a structured process for high-quality, atomic commits, saving you time and reducing complexity in version control.

Core Features & Use Cases

• Pre-commit Checks: Automatically runs linters, formatters, tests, and builds before committing, catching issues early.
• Atomic Commit Composition: Guides splitting distinct changes into separate, logical commits for cleaner history.
• Conventional Commit Messages: Enforces a standardized format for clear, searchable commit history and automated release notes.
• Use Case: After completing a bug fix, use this Skill to ensure your changes are clean, tested, and documented with a conventional commit message, making future rollbacks or feature tracking effortless.

Quick Start

In a Claude Code session, after making changes:

/commit

The Skill will guide you through:

1. Running pre-commit checks (mise run check, mise run test)

2. Reviewing staged changes and diff (git status, git diff --staged)

3. Determining commit strategy (single vs. multiple atomic commits)

4. Writing a conventional commit message (e.g., feat(auth): add password reset)