commit-helper

To generate conventional commit messages for git changes, this skill analyzes your current modifications and outputs a ready-to-use string formatted with the correct type, scope, and imperative subject under 50 characters.

The conventional commits specification for git workflow automation standardizes commit messages using types like feat, fix, or chore, along with an optional scope and body to make version control history readable and actionable.

To enforce a 50-character limit and imperative mood in git commit messages, this skill validates subject length between 1-50 characters and structures the phrasing to directly reflect the applied change.

Yes, this commit message generator supports optional body content and scope, allowing you to capture additional context needed for code reviews and accurate history tracing alongside the primary subject.

The best way to automate version-control messages for code reviews is to generate standardized, conventional commit text that clearly identifies the change type and scope, ready for direct execution with git commit.

Yes, you can use the generated commit message directly with git commit -m because the skill returns a properly formatted, ready-to-use string that requires no manual editing before execution.