pb-requesting-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 / PRD / spec?

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

Core principle: Review early, review often. A change can pass one axis and fail the other — reporting them separately stops one axis from masking the other.

When to Request Review

Mandatory:

• After each task in subagent-driven development
• After completing major feature
• Before merge to main