Coding
Get a real code review, not praise
Asks for problems ordered by severity, with the 'looks good!' response ruled out.
Prompt
Review this code as a senior engineer would in a pull request.
Context: {{context}}
This code will: {{purpose}}
```
{{code}}
```
Report only problems, ordered: correctness bugs first, then security, then performance, then maintainability.
For each: what's wrong | why it matters | a concrete failure case | the fix.
Do not compliment the code. If you find nothing in a category, say "none found" and move on. If something is a matter of taste rather than a defect, label it "preference" and put it last.Fill these in
Replace each highlighted variable before sending. Leaving them in place is the most common reason these prompts under-perform.
| Variable | What to put | Example |
|---|---|---|
{{context}} | Where this runs | Public API route, unauthenticated |
{{purpose}} | What it should do | Accept a form submission and store it |
{{code}} | Code to review | Paste the code |
Tips for better output
- "Do not compliment the code" removes most of the noise from AI reviews.
- The "concrete failure case" requirement filters out theoretical nitpicks.