What problem does it solve? Developers often create messy commit histories with vague messages, mixed changes, and broken intermediate states, making code review, debugging, and rollbacks painful. This Skill enforces atomic, well-described commits that keep the codebase in a working state at every point in history. ## Core Features & Use Cases - Conventional Commit Format: Structures messages with type prefixes (feat, fix, docs, refactor, test, chore), scope, and a 72-character summary, plus optional body and issue references. - Atomic Commit Enforcement: Guides splitting large changes into single logical units that pass tests and can be reverted cleanly. - Pre-Commit Verification: Requires tests, build, typecheck, and lint to pass before every commit. - Use Case: While implementing an authentication feature, you stage only the registration endpoint files and commit them as "feat(auth): Add user registration endpoint" with a body explaining the design, then separately commit the login endpoint, producing a reviewable, bisectable history. ## Quick Start Ask the AI to commit your current staged changes following clean-commits standards with a descriptive conventional commit message.
