Commits
Make the affected surface and intended change visible in the subject.
History
Why
A scoped commit is easier to inspect and revert than a batch of unrelated changes.
Rules
MUST follow the consumer's branch and commit authorization rules.[review]
MUST use Conventional Commits unless the repository specifies an established alternative.[review]
MUST choose a scope from the actual changed capability or package.[review]
MUST keep the subject imperative and identify breaking contracts explicitly.[review]
MUST inspect the worktree and complete diff before staging.[review]
MUST stage only the intended changes and exclude secrets.[review]
MUST fix hook failures rather than bypass them.[review]
MUST include the consumer's required release note when shipped behavior changes.[review]
MUST obtain release authorization independently of writing a release note.[review]
Example
[review]
Configured commit hooks validate their supported conventions. Review checks scope, release implications, and authorization.
Enforcement
Configured commit hooks validate their supported conventions. Review checks scope, release implications, and authorization.