code-review-agentteam

Two-axis review of the diff between HEAD and a fixed point the user supplies:

• Standards: does the code conform to this repo's documented coding standards?
• Spec: does the code faithfully implement the originating issue / spec?

Each axis runs in its own context, which is what keeps the two reports independent. This skill is the Lead's to run: every member gets the same team tools, but spawn_teammate and interrupt_agent refuse a teammate, so a teammate that needs this review asks the Lead for it.

The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.

Process

1. Pin the fixed point and freeze the diff

Whatever the user said is the fixed point (a commit SHA, branch name, tag, main, HEAD~5, etc.). If they didn't specify one, ask for it.

Confirm the fixed point resolves (git rev-parse <fixed-point>), the diff is non-empty, and the tree is clean (git status --porcelain). A bad ref, an empty diff, or a dirty tree fails here, not inside two teammates.

The reviewers can write to your checkout, so the diff can move while the reviews run. Freeze it once: write git diff <fixed-point>...HEAD to a patch file under a git-ignored path or outside the checkout, and record the diff hash. Hand both reviewers the artifact, never a command that re-reads a live tree.