review-changeslisted

Two-axis review of the diff between `HEAD` and a fixed point the user names. ## Fixed point Whatever the user names — a SHA, branch, tag, `main`, `HEAD~5`. Ask if they haven't given one. Before dispatching anything, confirm it resolves (`git rev-parse <point>`) and the diff is non-empty (`git diff <point>...HEAD` — three-dot, against the merge-base, so unrelated history on the fixed point's side doesn't show up). A bad ref or empty diff should fail here, not inside two parallel subagents. Also capture the commit list: `git log <point>..HEAD --oneline`. ## The two axes - **Spec** — does the change match what was asked? - **Standards** — does the change follow this repo's conventions, including the smell baseline below? Each runs as its own subagent so one axis's reasoning doesn't leak into the other's. ## Finding the spec Look in this order: an agreement already reached in this conversation, a spec file the user points at, or a spec file that matches the branch or feature name. If none of these turn up anything, don't invent a spec — the Spec axis reports "no spec available" and stops there. ## Finding the standards Whatever the repo documents — CONTRIBUTING, CLAUDE.md style notes, lint configs — plus the smell baseline in [references/smell-baseline.md](references/smell-baseline.md). The subagent can't read the plugin directory, so paste that file's contents into its prompt directly. Two rules bind the baseline: - documented repo standards override it — where the re