code-review

Three-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 issue / spec?
• Failure modes: what does a malformed, partial, slow or hostile input do at each external boundary in the diff?

All three axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings.

Run it once per branch, after the last task and before the PR opens. After an individual task or slice, keep implementing; review mid-branch only when the user asks for it.

The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.

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. On uncommitted work (as under implement), the three-dot form shows committed changes only: use git diff $(git merge-base <fixed-point> HEAD) and list the untracked files for the sub-agents to read.