| name | ship-commit-msg |
| description | Phase 9 commit message — write a Conventional Commit message from the staged diff. Mechanical, fast-tier. Use when: writing a commit message, summarizing a staged diff, or producing a Conventional Commit line. |
One-Liner
Turn the staged diff into one Conventional Commit message — type(scope): summary — describing what changed and why, not how.
Input: the staged diff. Output: a commit message.
Format (Conventional Commits)
<type>(<scope>): <summary ≤ 72 chars>
<body: what changed and why, wrapped>
type: feat, fix, refactor, test, docs, chore, perf, build, ci.- Summary in imperative mood; no trailing period.
- Body explains why (the what is in the diff); reference the feature/US id.
- Append the project's required trailer (e.g.
Co-Authored-By:) when configured.
Rules
- One logical change per commit. Do not commit unrelated changes together.
- Never include secrets or large generated blobs.
- Tier: fast — this is mechanical (see ../../resources/agent-tool-mapping.md).
Gate: the subject is <type>(<scope>): <summary> in imperative mood and ≤ 72 chars, the body
states why and references the feature/US id, the required trailer is present, and nothing secret or
generated is staged. If any check fails, fix the message — do not commit.
