commit-best-practices

Automated commit message generation analyzes your staged changes and produces concise, conventional messages following best practices—subject lines under 50 characters, imperative mood, and clear WHAT and WHY context—then presents them for approval before committing.

Conventional commits enforce standardized message formatting and structure. This Skill adapts messages to your repository's existing conventions, references relevant issues, ensures atomic commits, and uses AI-assisted generation so every team member produces consistent, meaningful messages without manual effort.

Yes. The /git-actions:commit command stages your changes, analyzes diffs, generates a message following best practices, presents it for approval, and executes the commit—automating the entire workflow while maintaining control through an approval step.

Conventional commits standardize message structure with clear subject lines, imperative mood, and explicit WHAT and WHY explanations rather than implementation details. Reviewers spend less time deciphering intent and more time evaluating code quality.

The Skill adapts generated messages to match your repository's existing conventions and style, so messages remain consistent with your team's established patterns while still following core best practices for clarity and atomicity.

Yes. The approval-driven workflow presents the generated commit message for your review before the final commit executes, giving you control and visibility into every change saved to git.