Code review & debugging21 categories
Write the PR description
Opening a pull request someone else has to review.
Write a pull request description for this change, aimed at a reviewer who has not seen the work. Sections: - **What changed** — two or three sentences - **Why** — the problem this solves, including what happens if we don't - **How to review** — where to start, which files matter most, which are mechanical - **How it was tested** — what I verified and how - **Risks** — what could break, what I am unsure about Be honest about the risks section. A reviewer who trusts it reviews better. 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
Commit message from a diffEvery commit. Especially the ones you'd otherwise call "fix stuff".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