PhraseryPhrasery homeGet Phrasery
Code review & debugging21 categories

Explain this bug to a teammate

Writing the incident note or the message that goes in the channel.

Mediumcommunicationdebugging
Write a short explanation of this bug for a colleague who has not seen the code: what goes wrong, under what conditions, and why it was easy to miss. Plain language, under 120 words, no code unless a single line makes it clearer.

Bug:

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

Commit message from a diffEvery commit. Especially the ones you'd otherwise call "fix stuff".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.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