What problem does it solve? Commit messages drift from the repository's established Conventional Commits format, especially on large multi-concern changes that drop the type prefix, and the commit-msg hook rejects malformed messages after the fact. ## Core Features & Use Cases - Format enforcement guidance: Covers the type(scope): subject shape, the type and scope vocabulary already in the git history, imperative lowercase subjects under 72 characters, and bodies that explain why. - Hook-aware workflow: Explains what the commitlint commit-msg hook enforces versus what it cannot judge, so messages pass on the first attempt without --no-verify. - PR title alignment: Ensures PR titles follow the same format since a squash merge turns the title into the commit subject. - Use Case: Before committing a refactor of the shell layout tokens, check the log for the existing shell scope spelling and write refactor(shell): read layout measurements from shared tokens with a body explaining the motivation. ## Quick Start Ask the assistant to write a conventional commit message for your staged changes following this repository's format before running git commit.
