Write a Commit Message From a Diff
Turn a diff into a clean Conventional Commits message — a tight subject line plus a body that explains the why.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
Write a commit message for the change below, following the Conventional Commits format.
Diff:
{{diff}}
Rules:
- Subject line: `type(scope): summary` — type is one of feat, fix, refactor, docs, test, chore, perf, build, ci. Keep it under ~72 characters, in the imperative mood ("add", not "added").
- Body (only if the change needs it): explain *why* the change was made and any consequence a reviewer should know — not a restatement of the diff.
- If the diff clearly contains more than one unrelated change, say so and suggest how to split it, rather than forcing a single message.
Return just the commit message, ready to paste.
Why this prompt works
-
How to Deploy an AI Agent
Every deployment problem follows from one property: you don't know how long a run takes, because you didn't write the path. Why the run m...
Read the guide → -
MCP Authorization and OAuth
Optional until you opt in, then very specific. Why the resource parameter is mandatory even when the server ignores it, why PKCE doesn't ...
Read the guide → -
MCP Transports: stdio vs Streamable HTTP
There are two transports now, not three, and the one that vanished is the one most tutorials still document. What each is exposed to, why...
Read the guide →