git-commit

To enforce Conventional Commits formatting, this Skill validates commits against rules requiring an explicit scope, present-tense imperative subject, maximum 50 characters, no trailing periods, and alignment with project-specific CLAUDE.md conventions to ensure consistent history.

A conventional commit message requires a type, a scope in parentheses, and a concise subject. The subject must use present-tense imperative mood, stay under 50 characters, contain no trailing periods, and avoid generic messages.

Avoid generic git commit messages by applying formatting rules that reject vague subjects, require an explicit scope, and align commits with repository-specific conventions defined in CLAUDE.md to maintain project standards.

Yes, you can use CLAUDE.md to define project-specific conventions. The Skill aligns commits with repository-specific rules in CLAUDE.md to maintain project standards while enforcing Conventional Commits format.

Your conventional commit subject fails validation if it lacks an explicit scope, exceeds 50 characters, uses non-imperative mood, includes trailing periods, or contains generic messages instead of concise descriptions.

Yes, stage changes with git add before committing. The Skill is applicable during everyday development tasks such as staging changes, creating commits, and documenting work across multiple repositories using Conventional Commits format.