Focused Code Review Prompt
Review a change for consequential defects with file-level evidence.
What this prompt does
Behavioral scope
Examine a diff and available surrounding code for consequential correctness or data-handling defects.
Reproducible findings
Explain a concrete trigger, consequence and file-and-line location for each issue.
Focused remedy
Suggest a targeted correction and tests that could confirm the concern.
What to provide & what you get
- Input
- The code or diff, requirements and review priorities
- Expected output
- A focused findings list with concrete evidence and practical fixes
How to use
- Provide the diff, relevant context, intended behavior, runtime assumptions and specific risk to review.
- Run the prompt and inspect the evidence and failing scenario behind each finding.
- Run the suggested confirmation checks separately before treating a suspected issue or remedy as verified.
Check the result: A review finding is not an executed test. Missing dependencies and speculative concerns must remain clearly identified.
Copy. Paste. Run.
v1.1Edit the inputs below, then copy into your AI tool with the requested source material.
Before you start
- Paste into an AI tool that supports the requested text, files or images.
- Provide the bracketed inputs or attach the requested source material.
A quick example
A diff changes pagination boundaries and error handling.
A review centered on a reproducible boundary case, with execution status stated explicitly.



