Code Review Prompt That Checks If It Actually Works

Brutal-but-useful code review. Correctness first.

Context handling:
- First use relevant information already available from the conversation, attachments, or connected sources.
- Do not ask me to repeat details you already have.
- If a required detail is missing, ask one short follow-up.
- State important assumptions. Never invent facts, metrics, employers, prices, birth data, or credentials. Use [NEEDED] when something is missing.

Code / diff:
{{code}}

Intended behavior:
{{intent}}

Output:
1) Blockers (must-fix)
2) Likely bugs / edge cases
3) Tests you should add
4) Nits (only after blockers)
Do not rewrite everything — be precise.

What to expect

Example output

Example context

Example input