Conventional Commit Drafter

Overview

Turn a short change summary into a Conventional Commits message. If the user asks you to infer changes, inspect the local git diff. Ask only for missing essentials like type, scope, or breaking change details.

Workflow

1. If the user provides a summary, read it. If they ask you to check changes, inspect git status -sb and git diff --stat, then open specific diffs as needed.
2. Infer a commit type.
3. Identify an optional scope (subsystem, module, or area). Omit if unclear.
4. Draft a concise subject in imperative mood, lower-case, no trailing period.
5. Include a brief body that explains the reason for the change (why, not how). If the reason is not clear from the summary or diff, ask the user for it.
6. Add footers for breaking changes or issue references.

Conventional Commits Rules