writing-commit-messages

To validate git commit messages, this skill checks your text against seven specific rules for subject line length, imperative mood, capitalization, period usage, body wrapping, and content focus. It clearly identifies and reports any deviations from established version control conventions.

The seven rules for writing effective git commit messages include enforcing subject line length, imperative mood, capitalization, and period usage. They also require body wrapping at 72 characters and focusing the content on the 'what' and 'why' to ensure a maintainable code history.

To check if your git commit subject line is properly formatted, this skill validates its length, verifies it uses the imperative mood, confirms proper capitalization, and ensures no trailing period is present, clearly flagging any violations for you to fix before committing.

Yes, the git commit message body wrapping limit matters for code review because this skill enforces a strict 72-character limit. Proper wrapping ensures messages remain readable in terminal interfaces and maintains a professional, maintainable version control history.

Git commit messages should focus on the what and why instead of the how because this skill strictly enforces this convention to improve code history quality. Explaining what changes occurred and why they were made provides clear context for future code review and maintenance.

Yes, you can use this tool to review past tense errors because it validates git commit messages against the imperative mood rule. It will flag if you used past tense instead of an imperative command, ensuring your version control conventions remain strict and consistent.