Code Review

Two-axis review of the diff between HEAD and a fixed point the user supplies:

• Standards: does the code conform to how this repo writes code?
• Spec: does the code faithfully implement the originating ticket / PRD / spec?

Both axes run separately so they don't pollute each other's context, then this skill aggregates their findings. Prefer parallel sub-agents when the harness supports them; otherwise run both reviews inline in sequence in this session. Either path must finish both axes before aggregating: never leave a review handle running past session end.

This is not a bug hunt. If the harness ships its own correctness review, that answers a third, different question (does it break?) and complements this skill rather than replacing it.

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 (when invoked from implement, it's the ticket's base commit).

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.