Loading…
Loading…
Most code review prompts fail the same way: you ask "is this good?" and get told yes. The prompts below are written to avoid that. They ask for specific lines, force a verdict, and in several cases explicitly instruct the model to try to prove the code wrong rather than praise it. Use them on a diff you are about to merge, a bug you cannot reproduce, or a file you inherited and do not trust yet.
36 prompts in 5 groups
Passes you run over a diff before it merges: correctness, security, concurrency, migrations.
Finding the cause when something fails, runs slow, or will not reproduce locally.
Making sense of an unfamiliar file, line or regex before you dare change it.
Cutting code down, naming things properly, and choosing between two workable options.
Commit messages, PR descriptions, and review feedback that lands the way you meant it.
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt