conventional-commit

A conventional commit message is generated by parsing staged diffs to infer the correct type, such as feat or fix, and formatting a commitlint-compliant message for your confirmation before applying it to the current branch.

Yes, the skill automatically infers the commit type from git staged changes by analyzing the diff content and classifying it as feat, fix, docs, style, refactor, test, or chore.

Yes, this conventional commit generator ensures commitlint compliance by formatting the inferred message to align with project standards, guaranteeing the resulting commit message passes commitlint validation before staging.

Yes, you need jq and rg installed. The skill relies on these dependencies to parse staged diffs and process the data required to generate your conventional commit message.

The best way to automate writing git commit messages for code reviews is using a diff-driven generator. This skill turns staged diffs into standardized conventional commits, streamlining releases and improving history readability.

To apply a generated conventional commit message to your current branch, simply confirm the suggested message during the workflow. The skill then stages and commits the changes directly to your current branch.