code-reviewlisted

Review the diff between `HEAD` and a fixed point the user gives you. - **Standards**: does the code follow this repo's documented conventions? - **Spec**: does the code do what the originating issue or spec asked for? Run both reviews as parallel sub-agents so they stay independent, then combine their findings. The issue tracker should already be available. If `docs/agents/issue-tracker.md` is missing, tell the user to run `/setup-matt-pocock-skills`. ## Process ### 1. Pin the fixed point Use whatever the user named - a commit SHA, branch, tag, `main`, `HEAD~5`, etc. Ask if they didn't specify one. Capture the diff once: `git diff <fixed-point>...HEAD` (three-dot, comparing against the merge-base). Also grab the commit list: `git log <fixed-point>..HEAD --oneline`. Before spawning agents, confirm the ref resolves (`git rev-parse <fixed-point>`) and the diff is non-empty. Fail early on a bad ref or empty diff rather than inside the sub-agents. ### 2. Find the spec Look for the originating spec in this order: 1. Issue references in commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.), fetched via `docs/agents/issue-tracker.md`. 2. A path the user passed as an argument. 3. A spec file under `docs/`, `specs/`, or `.scratch/` matching the branch or feature name. 4. If nothing turns up, ask the user where the spec lives. If they say there isn't one, skip the Spec sub-agent and note "no spec available" in the final report. ### 3. Find the standards Collect anythin