code-reviewlisted

Three-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 / spec? - **Adversarial**: how does the change fail in production? A different model runs this axis when one is installed, because sub-agents of one model agreeing is one reading repeated. All axes run as **parallel sub-agents** so they don't pollute each other's context. A validator sub-agent then checks every P0 and P1 with fresh eyes, and this skill aggregates what survives. The issue tracker should have been provided to you. If `docs/agents/issue-tracker.md` is missing, tell the user to run `/setup-supermatt-skills` (`$setup-supermatt-skills` in Codex). ## 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 the merge-base once with `git merge-base <fixed-point> HEAD`, create a fresh `mktemp -d` directory (`$DIR` below), and write the diff into it: `git diff <merge-base-sha> > "$DIR/diff.patch"` (against the merge-base, and including uncommitted changes to tracked files). That file is the diff every sub-agent reads: a shell hook can shorten a diff printed to the terminal, and a redirected one lands on disk whole. Also note the list of commits via `git log <fixed-point>..HEAD --oneline`. Before going further