Review my change before I ship it

For Claude Code, Cursor, an IDE assistant, the command line.

The prompt

Review this change. Here is the diff, and the full current content of each file it touches.

<diff>
{{DIFF}}
</diff>

<files>
{{FILES}}
</files>

Look for, in this order:
1. Anything that is wrong — logic errors, unhandled failures, off-by-one, race conditions.
2. Anything that will break something else in these files.
3. Anything handled badly rather than not at all.

For each finding: the line, what goes wrong, and a concrete input or state that triggers it.
If you cannot name how it fails, leave it out.
Do not comment on formatting, naming, or style.

What to fill in

Placeholder	What goes there
{{DIFF}}	git diff output
{{FILES}}	the full current content of each changed file

Why it works

Two instructions carry this one. Including the full files, not just the diff, stops the review flagging things that are handled three lines outside the diff window. And requiring a concrete failure case for every finding removes the generic advice that makes AI review tiring to read.

A review costs a cent or two. Run it on everything rather than on the changes you feel nervous about.

ShareOpen LinkedIn