What problem does it solve? Reviewing a PR, branch, or work-in-progress diff requires checking both spec fit and code quality against the exact current head, which is easy to get wrong when reviewers rely on stale assumptions or unverified bot comments. ## Core Features & Use Cases - Two-axis review: Maps each acceptance criterion to code, tests, and evidence while checking correctness, security, data integrity, and maintainability. - Structured findings: Every actionable finding includes severity, category, file:line evidence, impact, smallest safe fix, and a verification probe. - Bot claim verification: Disproves or confirms reviewer/bot comments against exact-head code, marking disproven claims as NOISE. - Use Case: Given a branch and a Linear task like SAN-123, pin the merge-base and head SHA, then produce a review that flags missing acceptance criteria and material risks without style trivia. ## Quick Start Ask the assistant to review this branch against main and the linked task spec, citing current-head evidence for every finding.
