Two-axis review of the complete change set between the current working tree 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?

Both 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. If docs/agents/issue-tracker.md is missing, tell the user to run /setup-repo-skills.

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.

Resolve the merge-base once, then capture the complete working-tree change set:

code-review