Independent review lanes for the complete change surface since a fixed point the user supplies. The surface includes commits, staged changes, unstaged changes, and untracked files:

Standards — does the code conform to this repo's documented coding standards?
Spec — does the code faithfully implement the originating issue / spec?
Frontend — when UI changed, does the rendered interface meet its design contract, responsive, interaction, accessibility, content, browser, and regression requirements?

Run every applicable lane in parallel so they do not pollute each other's context, then aggregate without allowing one lane to mask another.

The issue tracker should have been provided to you — run /setup-universal-agent-skills if docs/agents/issue-tracker.md is missing.

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 /implement invoked this skill, use the HEAD it recorded before implementation. Otherwise, if the user did not specify one, ask for it.

Capture the review surface once with all of these:

code-review

Process

1. Pin the fixed point