What problem does it solve? Git histories degrade when commit messages are inconsistent, over-length, or reference ephemeral context that reviewers cannot resolve. This Skill enforces Conventional Commits formatting, hard line-length limits, and atomic commit boundaries so that git log remains a readable decision record. ## Core Features & Use Cases - Deterministic message validation: A Python script checks header length (50 chars), Conventional Commits structure, blank-line separation, and body line length (72 chars), returning errors E1-E5 and warnings W1-W2. - Boundary discipline rules: Guidelines for splitting changesets into atomic, reviewable commits and avoiding spaghetti diffs and "and" commits. - Self-containment rules: Prohibits references to uncommitted artifacts (scratch files, workstream labels) so every message resolves from committed history or public URLs. - Use Case: Before committing a bug fix, run the validator on your drafted message; it fails a 60-character header or a missing blank line, and warns on non-imperative verbs like "added". ## Quick Start Ask the agent to validate your drafted commit message with the commit-hygiene checker before creating the commit.
