Write Conventional Commit
skill · v1.0.0
Produce a Conventional Commits message from a staged diff or change description. Enforces Code.md §11.2: correct type prefix, 72-char subject line, imperative mood, body explaining why not what, one logical change per commit.
Tags: gitcommitconventional-commitscode-style
Invocation contract
Inputs
diff_or_description(string, required) — Staged diff (git diff --cached output) or a prose description of the change.scope(string) — Optional scope hint, e.g. the module or package name.
Outputs
commit_message(string) — Full Conventional Commits message ready to pass to git commit -m.split_suggestion(string) — If the diff contains multiple logical changes, suggested split into separate commits.