Top pickEngineering and code
Thorough code review
Reviews a diff for bugs, security, performance and readability, ranked by severity with fixes.
Use it when
Before merging anything non-trivial.
What you fill in
- diff The diff or the changed code
- context What the change is supposed to do
The prompt
Review this change. It is supposed to: context diff Report findings ranked by severity (blocker, major, minor, nit). For each: file and line, the problem, a concrete failure scenario (inputs leading to the wrong result), and the fix as code. Check: correctness and edge cases, error handling, security (injection, auth, secrets, unsafe input), concurrency, performance, and whether tests cover the change. Only report issues you can tie to the code shown. If the change does not do what it is supposed to, say so first. Before you answer, check your draft against every instruction above and fix anything that misses.
Why it works
- Requires a concrete failure scenario per finding, which cuts false positives.
- Severity ranking tells you what blocks the merge.
- Checks intent against implementation first.