two-axis-reviewlisted

Two-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 spec / plan / PRD? Both axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings. ## 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. Capture the diff command once: `git diff <fixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log <fixed-point>..HEAD --oneline`. Before going further, confirm the fixed point resolves (`git rev-parse <fixed-point>`) and the diff is non-empty. A bad ref or empty diff should fail here — not inside two parallel sub-agents. ### 2. Identify the spec source Look for the originating spec, in this order: 1. A spec, plan, or PRD the user passed as an argument or that already exists in this conversation (for example an approved plan file). 2. A PRD/spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature. 3. Issue references in the commit messages (`#123`, `Closes #45`, etc.) — fetch with `gh issue view` when the GitHub CLI is available. 4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-ag