Code Review

Review a diff on two independent axes, each run by its own subagent:

• Standards — does the code follow this repo's documented conventions and avoid the baseline smells?
• Spec — does the code implement what the requirements asked for, ID by ID?

The axes are deliberately separate because a change can pass one and fail the other: flawless code that builds the wrong thing, or a faithful implementation that tramples the repo's conventions. Merged reports let one axis mask the other.

1. Pin the range — fail fast

Take the base ref the caller supplied (a sha, branch, tag, or merge-base). Confirm it resolves — git rev-parse <base> — and that git diff <base>...HEAD is non-empty. A bad ref or empty diff must fail HERE, not inside two parallel subagents. Also capture git log <base>..HEAD --oneline. If no base was given, ask. Done when: the ref resolves and the diff is non-empty.

2. Locate the spec

Find the governing requirements, in order: