pb-code-review

Part I — Requesting Review

When

Mandatory: after completing a task, before merging, before pushing to main. Optional: when stuck, before refactoring, after complex bug fix.

Two-Axis Review (parallel subagents)

Pin the fixed point first: git diff <fixed-point>...HEAD. Confirm diff is non-empty before spawning.

1. Standards axis — does code conform to AGENTS.md, CLAUDE.md, CONTRIBUTING.md? Plus Fowler smell baseline: Mysterious Name, Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Repeated Switches, Shotgun Surgery, Speculative Generality, Message Chains, Middle Man. Repo standards override baseline. Skip anything tooling enforces.
2. Spec axis — does code faithfully implement the originating spec? Look under specs/ matching branch name or issue refs in commits. If no spec, report "no spec available".

Output

Present two reports under ## Standards and ## Spec headings verbatim. Don't merge or rerank.