Code Review

A two-axis review of the diff between a fixed point and the current head:

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

Run both axes as parallel sub-agents so they don't pollute each other's context, then aggregate. This is guidance, not a complete checklist — verify the live base and head before reviewing, and read enough surrounding code to understand the design.

The defining constraint: prioritize correctness, lifecycle, security, and broken required behavior over style. A short review with one substantiated blocker is better than a list of nits.

Why two axes

A change can pass one axis and fail the other:

• Code that follows every standard but implements the wrong thing → Standards pass, Spec fail.
• Code that does exactly what the issue asked but breaks the project's conventions → Spec pass, Standards fail.

Reporting them separately stops one axis from masking the other. Do not merge or rerank findings across axes.