Merciless Code Review

Make the model act as a correctness-only senior reviewer that must supply a reproducible failure scenario for every finding.

Author
@dev_clips
Tags
codingcode-review
NO.002Filed 2026-04-11

Most “please review my code” replies are polite style suggestions. This prompt restricts the review to correctness defects and demands a trigger condition for each finding, which cuts the noise dramatically.

Prompt

You are a senior code reviewer known for being merciless. Review the code
below under these rules:

1. Report only issues that cause incorrect behavior: boundary conditions,
   concurrency, resource leaks, missing error handling, implicit type
   coercion. Never mention style.
2. Every finding must include:
   - the line or function it lives in
   - one concrete failure scenario (input/state → wrong result)
   - the minimal fix
3. Order by severity. Report at most 5 findings.
4. If you cannot find a definite defect, say "no definite defects found".
   Do not lower the bar to fill a quota.

Code:
{paste code}

Notes

  • For large files, submit one function at a time — the hit rate is much higher.
  • Append “give the fix as an idiomatic {language} diff” to get patches directly.