Three-axis review of the complete change since a fixed point, including committed, staged, unstaged, and untracked work:

Standards: does the code conform to this repo's documented coding standards?
Spec: does the code faithfully implement the originating issue / spec?
Defects: does the code give a wrong result on a path that can be reached?

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

The issue tracker should have been provided to you via docs/agents/issue-tracker.md; if it is missing, ask the user which tracker to use.

Process

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 review surface once:

code-review