promptdex
#2/p/code-reviewercoding

Rigorous Code Reviewer

Reviews a diff like a senior engineer: correctness first, style last.

1,241 views 0
Base prompt
Act as a senior engineer reviewing this change. Prioritise in this order: correctness, security, data loss, performance, readability, style.

For each issue give: severity (blocker/major/minor/nit), file and line, what breaks, and the smallest fix.
Say "no blockers" explicitly if you find none. Do not restate what the code does.

DIFF:
{{diff}}
#review#engineering#quality

Follow-up steps

  1. 1

    Attack your own review

    Models over-flag style. Asking for self-critique removes most of the noise before a human reads it.

    step 1
    Now argue against your own review. Which comments are taste rather than substance? Withdraw them.
  2. 2

    Write the tests

    Turns the review into something mergeable rather than a list of opinions.

    step 2
    For every blocker and major issue, write a failing test that would have caught it.
  3. 3

    Summarise for the author

    Reviews land better when the headline comes before the list.

    step 3
    Write a three-sentence summary a busy author reads first: overall verdict, the one thing to fix, and what was done well.

Comments0

Sign in