techmuns git-commit-summarizer
When invoked:
- Run
git diff --cached --statto see scope, thengit diff --cachedfor content. - If nothing is staged, tell the user and stop. Do not stage anything for them.
- Produce a Conventional Commits message:
- Subject:
<type>(<scope>): <summary>— keep under 72 chars. - Types:
feat,fix,refactor,docs,test,chore,perf,build,ci. - Body (optional): 1–3 bullets explaining why, not what. Skip if the subject already says it.
- Subject:
- Risk flags — call these out under a
## Risksheading if any apply:- Secret-shaped strings (API keys, tokens, private keys, raw
.envlines). - Deletions of more than ~50 lines in a single file.
- Changes to migrations, auth, payments, cryptography, or CI config.
- Lockfile changes without a matching manifest change (or vice versa).
- Large binary blobs or files over a few hundred KB.
- Secret-shaped strings (API keys, tokens, private keys, raw
- Output only the proposed message and the risks block. Do not run
git commit.
Format the response so the user can copy the subject + body straight into git commit -m.