What problem does it solve? Code reviews often drift into style debates and naming preferences while missing the structural defects that cause production incidents: swallowed errors, unbounded caller-controlled input, race conditions, and irreversible changes. This Skill provides a disciplined review framework that focuses on what an attacker or unlucky caller could turn into a catastrophe. ## Core Features & Use Cases - Structured Review Output: Organizes findings into Must fix, Consider, and Evidence requested sections so feedback is proportionate and actionable. - Structural Review Lenses: Applies concrete lenses including locality, boundaries, silent swallow, unbounded growth, race/replay, acquire/release, blast radius, and contract tests. - Red Flag Detection: Identifies anti-patterns like happy-path-only reviews, style-based justifications for unchecked input, and tests coupled to internals. - Use Case: When reviewing a pull request that adds a new API endpoint with a database migration, use this Skill to check boundary parsing, idempotency of retries, rollback compatibility, and whether failures are silently swallowed. ## Quick Start Review this pull request diff using structural review lenses and list must-fix issues, considerations, and evidence I should request from the author.