commit-message

To generate a conventional commit message from a git diff, the skill reads your staged changes and current branch name to infer the correct type and scope. It then structures the body by topics to produce a clear Commitizen-style title and body.

Automatic commit type and scope inference works by analyzing the content of your git diff. The skill applies Commitizen rules to map the detected changes to the appropriate type and scope, forming a structured title like type(scope): subject.

When nothing is staged in git, the skill identifies the empty staging area and handles the scenario by prompting you for review before committing. This prevents empty commits and ensures you review changes first.

The best way to structure a commit body by topics is to group related changes identified in the diff. This skill automatically categorizes diff sections into concise, topic-based lines for a readable commit history.

You do not need Commitizen installed externally to format your git commit messages. The skill applies Commitizen rules internally to generate the conventional commit format directly from your diff and branch name.

Yes, you can use your current branch name to determine the commit scope. The skill reads the branch name alongside the diff to accurately infer the scope and structure the Commitizen-style title.