commit-helper

Angular-style commit messages follow a structured format with type, optional scope, subject (max 50 chars), wrapped body (72 chars), and optional footer. This Skill analyzes your staged Git changes and generates a properly formatted message automatically, eliminating manual formatting work and ensuring consistency across commits.

Yes. After staging changes with Git, this Skill analyzes the diff and generates a complete Angular-format commit message with appropriate type, scope, subject, and body sections, saving time and reducing formatting errors in your development workflow.

Angular commit conventions standardize messages with type prefixes (feat, fix, docs, etc.), optional scopes, concise subjects, and detailed bodies. They improve readability, enable automated changelog generation, and maintain consistent project history—this Skill automates adherence to these standards.

Yes. This Skill generates conventional commit messages compliant with Angular style, applicable to local development and code-review workflows. It ensures your staged Git diffs produce correctly formatted messages with all required sections and character constraints.

The Skill processes git diff --staged output to understand what code changed, then generates a message with the appropriate type, scope, and description that accurately reflects those changes while adhering to Angular commit format constraints.

This Skill enforces Angular format constraints during generation: enforcing type classification, limiting subject lines to 50 characters, wrapping body text at 72 characters, and including optional footers for breaking changes or issue references—ensuring compliance automatically.