Review the diff between HEAD and a fixed point the user names, along two independent axes:

Standards — does the code obey this repo's documented coding standards?
Spec — does the code actually build what the originating issue / PRD / spec called for?

Each axis runs in its own parallel sub-agent so neither one contaminates the other's context; this skill then gathers their findings together.

You should already have the issue tracker on hand — run /setup-skills if docs/agents/issue-tracker.md is missing.

Process

1. Pin the fixed point

The fixed point is whatever the user gave you — a commit SHA, a branch name, a tag, main, HEAD~5, and so on. If they gave you nothing, ask.

Lock in the diff command once: git diff <fixed-point>...HEAD (three-dot, comparing against the merge-base). Grab the commit list too: git log <fixed-point>..HEAD --oneline.

Before you go any further, verify the fixed point resolves (git rev-parse <fixed-point>) and the diff has content. A dead ref or empty diff should blow up right here — not deep inside two parallel sub-agents.

code-review

Process

1. Pin the fixed point