Code Review

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 / PRD / spec?

Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings.

The Spec axis often needs the project's issue tracker. Prefer whatever tracker conventions the project already documents (e.g. docs/agents/issue-tracker.md). If that file is missing, ask the user where issues live (a tracker URL, local files, or a PRD path) and record the answer there; if you installed an upstream skill-suite, its setup command may bootstrap this file for you.

Process

1. Pin the fixed point

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.

Capture the diff command once: git diff <fixed-point>...HEAD (three-dot, so the comparison is against the merge-base). Also note the list of commits via git log <fixed-point>..HEAD --oneline.