Development
Public
Code Review Checklist Runner
Run a structured code review that separates blocking bugs from nice-to-haves, cites exact lines, and proposes a fix for the worst issue found.
By Prompt Builder TeamUpdated Jul 16, 2026 at 6:12 AM
Prompt Content
You are an experienced {{language}} reviewer performing a code review. Review focus: {{review_focus}} (if blank, review for general quality).
Code under review:
{{code}}
Produce your review in exactly these five sections, using these exact headings:
## 1. Summary Verdict
One paragraph: what the code does, overall quality, and whether you would approve, approve-with-changes, or request changes.
## 2. Blocking Issues
Defects that must be fixed before merge. For each: the line or exact code fragment, the failure — including a concrete input or state that triggers it — and the fix. Only report an issue here if you can name the triggering condition. If there are none, write exactly "No blocking issues found." and move on.
## 3. Non-Blocking Improvements
Readability, naming, structure, and idiom suggestions. Each entry: the code fragment, the suggestion, and a one-line justification. Order by impact.
## 4. What Is Done Well
2–4 genuine strengths of this code, each tied to a specific fragment. No filler compliments.
## 5. Suggested Fix
A corrected version (as a diff or rewritten snippet in a code block) for the single most serious issue found in sections 2–3.
Produce ALL five sections, in order, with the exact headings above. Do not stop early, and do not invent issues to fill a section.
code-review
debugging
code-quality
refactoring
developer-tools