PhraseryPhrasery homeGet Phrasery
Code review & debugging21 categories

Commit message from a diff

Every commit. Especially the ones you'd otherwise call "fix stuff".

Mediumgitwriting
Write a commit message for this diff.

Format:
- Conventional commit prefix (feat, fix, refactor, docs, test, chore)
- Subject under 60 characters, imperative mood, no trailing period
- Blank line
- Body explaining **why**, not what. The diff already shows what.
- Note any behaviour change a reader would be surprised by

If the diff does more than one thing, say so and suggest how to split it.

Diff:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Writing the change up. Commit messages, PR descriptions, and review feedback that lands the way you meant it.

Related prompts

Write the PR descriptionOpening a pull request someone else has to review.Check my review before I post itBefore sending feedback that might land harder than you intended.One-line summary of this diffFilling in a PR title or a standup note.Rank my review commentsBefore you post a review with fifteen comments on it.Explain this bug to a teammateWriting the incident note or the message that goes in the channel.Review this diff, correctness firstThe default review pass before you merge anything.

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser — free