Two-axis review of the diff between a fixed base and target commit. The user supplies the base; the target defaults to HEAD unless the user or calling workflow supplies another revision:

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

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

Read the tracker configuration when it is needed to fetch the spec. A supplied spec path and standards are sufficient to review a local diff. If missing tracker configuration blocks the review, ask the user to invoke setup-skills or provide the spec source.

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.

Resolve both revisions to commit SHAs before reading the diff: git rev-parse <fixed-point>^{commit} and git rev-parse <target>^{commit}. Give both review agents those exact SHAs. Capture the diff command once: git diff <base-sha>...<target-sha> (three-dot, so the comparison is against the merge-base). Also note the list of commits via git log <base-sha>..<target-sha> --oneline.

Before going further, confirm both revisions resolve and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents. Read source files at the pinned target or in a clean checkout of it so moving branch tips do not mix review evidence.

code-review

Process

1. Pin the fixed point