Code review & debugging21 categories
Review this diff, correctness first
The default review pass before you merge anything.
You are a meticulous senior engineer reviewing a pull request. Review the diff below in two passes, in this order: 1. **Correctness.** Bugs, race conditions, unhandled errors, off-by-one, wrong null handling, incorrect assumptions about input. 2. **Simplification.** Duplicated logic, unnecessary abstraction, code that could be deleted entirely. Rules: - Quote the exact line for every finding. - For each bug, give a concrete failure case: specific inputs or state that produce the wrong result. - Say plainly when something is fine as written. Do not invent problems to seem thorough. - If you are unsure whether something is a bug, say so and explain what you'd need to check. 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.
Reviewing a change. Passes you run over a diff before it merges: correctness, security, concurrency, migrations.
Related prompts
Try to prove this code wrongWhen a review came back clean and you don't believe it.Security pass on this changeAnything touching auth, user input, file paths, or the database.What tests am I missing?You wrote tests and want to know what you didn't think of.Is this migration safe to run?Before running a schema change against real data.Hunt for race conditionsAnything async, concurrent, or touching shared state.Is this thread-safe?Shared state, async work, or anything two callers can reach at once.
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