PromptDev
Review a code change
A reviewer prompt that ranks findings by severity, separates bugs from taste, and must say "nothing blocking" when that's the truth.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Review this code change as a senior engineer. Context: adds retry logic to our payment webhook handler.
Report findings in severity order: first anything that is a BUG (wrong output, crash, security hole, data loss) with the concrete scenario that triggers it; then risks (missing error handling, races, performance cliffs); last, style points — clearly labelled as optional. For each finding, quote the exact line and propose the fix. Do not pad the review: if the change is sound, say "nothing blocking" and stop. Do not invent requirements the change was never trying to meet.
The change:
[paste the diff or the changed functions here]
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →Severity ordering with a bugs/risks/style split stops the classic AI-review failure — ten equal-weight comments where the one real bug hides between two naming nitpicks.
- →Requiring a triggering scenario per bug filters confident-sounding false positives: a "bug" that can't name its failing input usually isn't one.
- →Licensing "nothing blocking" matters — without it, models manufacture findings to look thorough.