What problem does it solve?
This Skill solves the problem of messy, unparseable git commit history that hinders changelog generation, semantic versioning, and code review. It enforces the Conventional Commits specification, ensuring each commit represents one atomic behavior change, making project history clear and automated tooling reliable.
Core Features & Use Cases
- Atomic Change Enforcement: Guides users to split mixed changes into single, atomic behavior units using
git add -p, preventing "monolithic" commits.
- Semantic Commit Formatting: Prescribes the
<type>[scope]: <imperative> format for commit messages, enabling automated changelog generation and semantic versioning.
- Pre-Commit Verification: Encourages verifying staged changes (
git diff --cached) against the intended commit message before committing, reducing errors.
- Use Case: When a developer has simultaneously fixed a bug and added a new feature, this Skill guides them to use
git add -p to create two separate, semantically correct commits: one for the fix and one for the feat.
Quick Start
When you have mixed changes in your working directory, use 'git add -p' to stage related hunks for a single atomic behavior change, then commit with a Conventional Commit message like 'feat(auth): add magic-link login'.
