VerdictPal
Join
GuidesPlaybook

Coding-agent PR review

A pull-request review packet with diff summary, test evidence, risk notes, and rollback steps.

Advanced
Start now
Playbook

Coding-agent PR review

A pull-request review packet with diff summary, test evidence, risk notes, and rollback steps.

Steps5Time~61 minArtifactPR review packetLeveladvanced
Before you start
  • Comfortable with git and pull requests
  • Experience with AI coding assistants
Tools in this guide
LinearCursorClaudeWarp
0%0/5 steps

Solo builder · 45–70 minutes

The agent can write the diff. It cannot be accountable for it.

This runbook makes every agent change explainable before it leaves your branch.

PR review packet

PR review packet

Diff intent, changed files, test proof, security notes, and rollback line in one review comment.

Write the intent lock

8 minLinear

State the bug or feature, files likely involved, and what must stay unchanged.

A three-line intent lock.
Pitfall
Letting the agent discover scope by editing.
Verification
The final diff can be compared to the original intent.

Generate the smallest diff

20 minCursor

Ask Cursor or Factory for one narrow implementation and explicitly forbid opportunistic refactors.

A focused branch with no unrelated cleanup.
Pitfall
Accepting a prettier architecture when the task needed a local fix.
Verification
Every changed file maps to the intent lock.

Ask for the uncomfortable diff review

15 minClaude

Have a second model list regression, security, accessibility, and data-shape risks from the diff only.

Risk list sorted by blast radius.
Pitfall
Asking 'does this look good?' and receiving reassurance.
Verification
At least one plausible failure path is tested or dismissed with a reason.

Produce proof

10–20 minWarp

Run the smallest relevant validation and capture the command, result, and any skipped checks.

Test evidence block.
Pitfall
Claiming confidence from TypeScript when the risk is product behavior.
Verification
The PR text says what passed and what was not checked.

Ship the review packet

8 min

Write the final PR note: intent, diff map, user-visible change, proof, risks, rollback.

A PR comment a maintainer can audit in two minutes.
Pitfall
Letting the generated code be the only documentation of the change.
Verification
A reviewer can decide whether to merge without reconstructing your prompt session.
Finish line

You should now have: PR review packet.

  • Every changed file is justified by the intent lock.
  • The review packet names at least one risk and how it was handled.
  • Validation evidence is specific; no generic 'looks good' line survives.

PrivacyDo not paste private repository secrets, customer data, or proprietary incident details into consumer coding tools. Redact logs before asking a model for review.