Git Commit Helper

Conventional commit messages follow a structured format with type, scope, and subject. Stage your changes with `git add`, then ask the Skill to analyze your diff and generate a message adhering to conventional commit standards like `feat(scope): description` or `fix: resolve issue`.

Conventional commits are a standardized format for Git messages that specify type (feat, fix, docs, refactor, test, chore, style), scope, and description. They improve code review clarity, enable automated changelog generation, and maintain consistent version control history across frontend, backend, docs, and infrastructure.

Yes, the Skill handles both single-file and multi-file commits. It analyzes staged diffs across all changed files to surface relevant type, scope, and descriptions, then suggests a compliant message that covers all modifications.

The Skill supports interactive workflow and amend operations. After generating an initial message, you can request modifications to refine type, scope, subject length (under 50 characters), imperative mood, or add breaking-change notes before finalizing.

The Skill enforces conventional commit types: `feat` for features, `fix` for bug fixes, `docs` for documentation, `style` for formatting, `refactor` for code restructuring, `test` for test additions, and `chore` for maintenance tasks, with optional breaking-change notation.

Yes, the Skill applies across frontend, backend, docs, and infrastructure diffs. It analyzes changes in any domain to determine appropriate type and scope, then generates messages that comply with conventional commit guidelines for mixed-change commits.