Code review

Review a diff and report what's wrong with it. Change nothing. Rules follow the workflow contract.

Inputs

A working tree, branch, PR, or commit range; its base; and the ticket or request that states what it should do. Orchestrate also passes the diff fingerprint and, for a follow-up review, the head to review changes since and the earlier findings.

Modes

• Author QA: the author asks before opening a PR. It can block the PR, but it never counts as review evidence.
• Independent: requested by Orchestrate or a user, in a fresh session with none of the implementation conversation. This is the review a merge needs. If your session isn't fresh, say so and stop.