Codereview

A Claude Code patch enters an independent evidence review before the agent explanation is revealed in a second pass

Do not let Claude Code explain its patch to the evaluator first

A polished Claude Code handoff can anchor the reviewer before the evidence is checked. Give an independent evaluator the task contract, patch, and raw test results first, then reveal the agent’s explanation.

A Claude Code test denominator records expected, discovered, selected, executed, skipped, and missing tests before a review can pass

Make Claude Code report the tests it did not run

A green test result says little when the agent selected the wrong suite or skipped the risky path. Add a test denominator to every Claude Code review packet.

Two passing Claude Code test commands point to different commit, working tree, and lockfile fingerprints, so the review marks one result stale and requests a rerun

Bind Claude Code test results to the code they actually tested

Claude Code can report passing tests from different repository states. Add a run fingerprint so each result names the exact code, dependencies, tools, and policy it tested.

A shared working tree enters a diff ownership gate where Claude Code changes continue to review while a developer edit and unattributed generated file are excluded

Make Claude Code prove diff ownership before it commits

Claude Code can accidentally include a developer’s unfinished edit or another agent’s output in its patch. Record the baseline, attribute every hunk, and block commits when ownership is unclear.

An approved Claude Code plan bound to commit A reaches a freshness gate after commit B changes a relevant dependency, so execution stops and the agent replans for review

Expire Claude Code plans when the repository changes

A Claude Code plan can become stale after another commit changes its assumptions. Bind approval to repository state and force a replan when the relevant boundary moves.

A tested Claude Code commit changing after a rebase, causing a release gate to reject stale evidence and run the checks again

Your green check belongs to a commit, not a pull request

A Claude Code branch can change after tests pass and approval is given. Bind test results, review evidence, and release approval to the exact commit that produced them.

A Claude Code run replay record connecting the task contract, agent actions, decision points, evidence packet, human review, and incident replay

A diff cannot replay a Claude Code run

A Claude Code diff shows the final change, but it leaves out the starting state, failed commands, MCP results, skipped tests, and plan changes. Capture a compact replay record before the run disappears.

A Claude Code agent run leaving receipts for changed files, tests run, logs captured, risk notes, and undo path

Claude Code needs permission receipts, not blanket trust

Claude Code permissions matter before the run, but teams also need permission receipts after the run: what the agent used, what was blocked, what still needs approval, and how to undo it.

A diagram showing an agent bringing proof into a review packet with intent, diff map, tests, risk note, and rollback

Claude Code diffs need review packets, not trust

A Claude Code diff shows the changed lines. A review packet shows the delegated intent, scope, checks, risks, and rollback path a human needs before merge.

A review packet checkpoint between a Claude Code diff and a production merge

Claude Code review packets beat clean diffs

A clean Claude Code diff is a weak production signal. Ask for a review packet with scope, tests, gaps, rollback, and human inspection notes before merge.