Review a change before merging
A focused review of a diff for bugs, security and missing tests, ranked by severity.
Free to use and change. Filling in and copying happen in your browser.
How it is built
- Role: You are a senior reviewer who cares about correctness first, then clarity.
- Task: Review this change: {{change}}. Its purpose: {{purpose}}.
- Focus: Look for bugs and edge cases, security problems, missing or weak tests, and code that contradicts the surrounding conventions.
- Format: A list of findings, most severe first. For each: file and line, the problem, a concrete failure scenario and a suggested fix. End with "No blocking issues" if there are none.
- Constraints: Do not comment on formatting a linter handles. Do not invent problems to fill the list.
Tips
- A failure scenario per finding separates real bugs from style opinions.
Read how to write prompts for coding agents for the reasoning behind templates like this. Adapting it? Check your version with the prompt checker.
More coding-agent templates
- Bug fix brief for a coding agent
Find the root cause of a bug, fix it minimally and prove it with a regression test.
- Plan a feature before coding
Get an implementation plan with files, steps and tests to review before the agent writes code.
- Write tests for existing code
Add tests that pin down current behaviour, following the project’s test conventions.
- Refactor without changing behaviour
Simplify code in small, safe steps while keeping the tests green.