Git Commit Helper

Generate a commit message by analyzing your staged changes with `git diff --staged`. This Skill reads the diff output and produces a conventional commit message that follows best practices with an imperative mood, scope, and type (feat, fix, refactor, etc.), ensuring your Git history remains clear and consistent.

Conventional commits is a structured format for Git messages that specifies type, optional scope, and subject line under 50 characters, optionally followed by a body and breaking-change notes. This standardization improves version control readability, enables automated changelog generation, and makes collaboration easier across teams.

Yes. This Skill enforces imperative mood, concise subjects under 50 characters, conventional commit types (feat, fix, docs, style, refactor, test, chore), optional scope, and optional body text. It includes a checklist to ensure your messages are focused, informative, and maintainable for long-term project history.

This Skill parses `git diff --staged` output to extract all changes you've prepared for commit. It analyzes the diff content and generates a descriptive message that accurately reflects your modifications, then formats it as a conventional commit with appropriate type classification.

Yes. This Skill supports optional breaking-change notes in the conventional commits format, allowing you to flag API-breaking or major behavioral changes alongside your commit type and description for clear communication to maintainers and users.