Codereview

A production Claude Code workflow showing scope, patch, tests, review, and rollback as required controls

Do not merge Claude Code work without a review packet

A clean Claude Code diff is not enough for production review. The reviewer needs the task contract, scope, commands, evidence, risks, rollback note, and approval record before merge.

A Claude Code review packet diagram with task contract, evidence, boundary pressure, and rollback note

Before you merge Claude Code's work, ask for the receipt

Passing tests are a useful signal, but they are not enough for production Claude Code work. Ask for a review packet that shows scope, evidence, boundary pressure, remaining risk, and rollback before merge.

Diagram showing a Claude Code handoff record from task boundary to patch evidence, risk note, rollback, and reviewer decision

Claude Code handoffs fail when the run record is vague

Claude Code can produce a working patch and still leave the next human with a weak handoff. Production teams need run records that show scope, evidence, risk, and rollback before review turns into archaeology.

Diagram showing green tests as one signal beside a Claude Code review packet with scope, command log, tool log, rollback note, and human approval

Claude Code green tests are not a review packet

A Claude Code run can make tests pass and still leave a reviewer with no usable evidence. Treat green tests as one signal, then require scope, command logs, tool use, assumptions, and rollback notes before merging agent work.