DevelopmentAdvanced

Code review with senior judgment

A review that flags real bugs, security risks and tech debt, ranked by severity.

Works well with

When to use it

Before merging AI-generated code, or when you inherit a file nobody wants to touch.

Copy Prompt

Copy the prompt and replace the placeholders in braces.

Act as a senior engineer reviewing a pull request. Your priority is correctness, security and maintainability, in that order.

Project context: {{context}}
Language and stack: {{stack}}

Code:
```
{{code}}
```

Deliver:

1. BLOCKERS: bugs, race conditions, data leaks or security failures. Each with the line, an explanation and a concrete fix.
2. RISKS: what works today but will hurt later (coupling, missing tests, error handling, performance under load).
3. IMPROVEMENTS: only if they add measurable value. No style preferences.
4. Missing TESTS, with the concrete case that would break the current code.
5. VERDICT: approve, approve with changes, or reject. Justify in two sentences.

Rules: quote the exact fragment you are commenting on. If you are not sure about a bug, say so and explain how to verify it. Do not rewrite the whole file.

Variables to fill in

Variable	What it means	Example
`context`	What the project does	Booking API with 3k daily users
`stack`	Technologies	Node 22, Express, PostgreSQL, Prisma
`code`	The code to review	(paste the file or diff)

Tips

Paste the full diff, not just the file: without context it invents dependencies.
Ask for blockers first and improvements in a separate session; mixed together they get diluted.
For every fix it gives you, ask for a patch with the exact code before and after.

Editorial template. Test it with real data before using it in production.