code-review

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 issue / spec?

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

Read configured tracker and project artifacts when the spec requires them; a local spec or the accepted task brief does not require tracker setup. Invoke /pstack-swarm for host-native independent review and disclosed fallback.

Process

1. Pin the fixed point

Whatever the user said is the fixed point (a commit SHA, branch name, tag, main, HEAD~5, etc.). Reuse a fixed point already supplied by the invoking workflow. If none is established, propose the repository's actual merge-base; ask only when the intended scope is ambiguous.

Resolve the base and reviewed head to immutable SHAs. For a committed branch use their merge-base diff. For requested working changes include staged, unstaged, and relevant untracked files in a captured snapshot, and record their hashes. Both axes review the same artifact. Also record the commit list for a committed scope.

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.