What problem does it solve? Large code reviews often overwhelm reviewers and produce shallow results. This Skill structures a senior-level systems code review into three gated phases, ensuring thorough coverage of architecture, individual files, and cross-cutting issues without losing rigor. ## Core Features & Use Cases - Phased Review Workflow: Runs a repo overview, file-by-file drill down, and cross-cutting analysis as separate phases, pausing for explicit user approval between each. - Persistent Findings File: Writes all findings to a single code.md file, appending per phase so results survive long sessions. - L6-Style Systems Focus: Targets logical errors, unhandled edge cases, architectural mismatches, and future breakpoints rather than style nits. - Use Case: Point it at an unfamiliar repository before a major refactor; get a structured architecture map first, approve it, then receive per-file and cross-cutting analysis you can act on incrementally. ## Quick Start Ask the assistant to run a phased code review of this repository and write the findings to code.md.
