write-commit-message

To enforce git commit message formatting, this Skill drafts subjects under 50 characters and wraps body text at 72 characters using a line-counting script. It validates capitalization, imperative mood, and blank-line separation before finalizing commits.

Automating commit message linting involves running validation scripts that detect structural violations in version control systems. This Skill executes provided lint and count tools to verify formatting standards across git, jj, and sapling when creating or amending commits.

No external dependencies are required to use this commit message formatter. The Skill operates independently using its built-in scripts and references to validate subject length, capitalization, imperative mood, and body wrapping without needing additional packages.

Commit message subjects use imperative mood and avoid trailing periods to follow established VCS guidelines, keeping git history readable and actionable. This formatting standard ensures changelogs and code reviews remain consistent and clear for all contributors.

To prepare a standards-compliant commit message for a pull request, draft a concise subject and explanatory body, then run validation scripts. This Skill enforces formatting rules, executes lint checks, and returns a final lint-passing message ready for merging.