review
Three-axis review of the diff between a fixed point the user supplies and HEAD:
- Standards — does the code conform to this repo's documented conventions, and does it steer clear of the smell baseline below?
- Spec — does the code faithfully implement the originating issue / PRD / spec?
- Architecture — does the change go with the grain, keeping the system coherent and cheaper to change — or cut across it?
Each axis runs as a parallel sub-agent so they don't pollute each other's context, then this skill aggregates their findings. The separation is the point: a change can pass one axis and fail another, and a single reviewer collapses them.
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). Note the commit list via git log <fixed-point>..HEAD --oneline.
Confirm the fixed point resolves (git rev-parse <fixed-point>) and the diff is non-empty before going further. A bad ref or empty diff fails here — not inside three parallel sub-agents.