git-commit

To enforce standardized git commit messages, this Skill applies 7 rules governing subject formatting, body structure, and imperative tone across any code change workflow. It guides teams to craft concise messages, reducing confusion during reviews.

Git commit messages use the imperative mood to ensure actionable, standardized commits. This Skill enforces this tone, requiring phrases like "Add" instead of "Added" so the history reads as clear instructions.

The maximum character length for a git commit subject line is 50 characters. This Skill enforces this subject length control along with capitalization rules and no trailing periods to maintain concise, uniform project history.

Yes, you can use this commit message standard for both feature and bugfix workflows. It applies to any code change workflow, including refactoring, ensuring uniform message formatting across multiple developer contributions.

The best way to format git commit bodies is to provide optional guidance explaining what and why the change was needed. This Skill enforces body structure rules to help teams communicate intent and rationale clearly.

To write your first standardized git commit message, use the template: git commit -m 'Add feature' -m 'Explain why this change is needed.' This format separates the concise subject from the explanatory body.