Code review & debugging21 categories
Check my review before I post it
Before sending feedback that might land harder than you intended.
Here is code review feedback I'm about to post. Check it before I send it. - Is anything factually wrong or unfair? - Which comments are matters of taste stated as if they were rules? Mark them as preferences. - Is anything blocking that shouldn't be, or non-blocking that should be? - Does any of it read as harsher than intended? Suggest rewording that keeps the substance. - What did I miss that a reviewer should have caught? Keep my directness. I want it accurate and kind, not softened into vagueness. My review:
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.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