git-commit-writer

You can generate a conventional commit message from a git diff by analyzing your code changes and change intent. The skill applies type validation, scope inference, and imperative mood to output a spec-compliant commit message.

You can validate an existing commit message against the Conventional Commits 1.0.0 specification. The skill checks your message for correct format, mood, scope, and breaking-change rules to ensure full compliance.

Scope and type inference works by analyzing changed files and change intent to determine the appropriate category like features, fixes, docs, or CI updates. This process automatically maps your code modifications to the correct conventional commit type.

When your git diff is ambiguous for commit message generation, the skill triggers human-review escalation. It uses confidence thresholds and asks clarifying questions rather than guessing the commit type or scope unreliably.

Yes, the conventional commit writer enforces subject length limits and imperative mood. It ensures your generated commit messages strictly follow formatting rules required by the Conventional Commits specification.