Code Review

Run a standards-backed code review. This is review-only: do not edit files, apply patches, or "fix as you go" unless the user explicitly asks after the review.

Treat ../coding-standards/ as the standards package. Load standards by topic; do not duplicate or reinvent them here.

Review principles

• Review changed behavior, contracts, seams, tests, and runtime effects — not style vibes.
• Every finding needs proof: a concrete path, location, missing contract, reachable failure, leaked value, unparsed boundary, invalid state, or inadequate test seam.
• Preserve local conventions when compatible with the standards; do not use local convention to excuse correctness, safety, boundary, observability, or test-integrity violations.
• Prefer fewer, stronger findings over exhaustive commentary.
• Do not include praise or a "what's good" section.

1. Select the review target

Use the user's explicit target when provided: files, commit range, branch, PR, diff, or staged/unstaged scope.

When no target is provided, detect it: