commit-message

To generate conventional commit messages from git diff, the skill reads staged or full diffs to identify the change type and optional scope, then formats them into `type(scope): description` with an optional body and footer.

The character limit for a conventional commit description is 72 characters. The generated messages enforce imperative lowercase English descriptions to ensure repository hygiene and keep history automation-friendly.

To format breaking changes in a conventional commit message, the skill produces breaking-change metadata using the `BREAKING CHANGE:` footer notation based on the analyzed git diff to maintain clear repository history.

Yes, you can use this for chore maintenance and documentation updates. The skill supports committing code changes, tests, refactors, and CI maintenance by analyzing the actual diff to infer the correct commit type.

Yes, the skill works with unstaged changes. It analyzes staged changes via `git diff --cached` or all unstaged changes via `git diff` to infer the appropriate commit type and scope for generating the message.

The best way to maintain repository hygiene with conventional commits is generating one commit per change using `type(scope): description` formatting, which keeps history readable and automation-friendly across common repositories.