Two-axis review of the requested changes, whether committed or still in progress:

Standards: does the code conform to this repo's documented coding standards?
Spec: does the code faithfully implement the originating issue / spec?

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

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.

For committed work, capture git diff <fixed-point>...HEAD and git log <fixed-point>..HEAD --oneline. For work in progress, also capture the staged and unstaged changes (git diff --cached, git diff) and inspect relevant untracked files from git status --short. Freeze the requested file set and diff for both reviewers so they review the same version. Exclude unrelated working changes.

Before going further, confirm the fixed point resolves (git rev-parse <fixed-point>) and the requested review surface is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents.

code-review

Process

1. Pin the fixed point