What problem does it solve? Codebases accumulate structural debt—wrong abstractions, misleading signatures, dead code, and misplaced dependencies—that simple cleanup cannot fix. This Skill diagnoses whether a component's design premise is sound and produces a structured, evidence-backed refactor proposal, so engineers can decide what to change before touching any code. ## Core Features & Use Cases - Premise-first diagnosis: Identifies the single upstream design decision causing multiple symptoms, rather than cataloguing surface-level issues one by one. - Four-phase workflow: Surveys callers and dependencies with real tools (ripgrep, language servers, ts-prune, knip), diagnoses root causes, proposes changes with confidence tiers, and reports in a structured Refactor Proposal format. - Hard-stop safety gates: Flags public exports, HTTP routes, database schemas, event payloads, and feature flags for explicit per-item sign-off before any change is recommended. - Use Case: Point it at a tangled module and ask "is this design right?"—it returns a proposal naming the wrong abstraction, the reversal that fixes it, real call-site counts, and confidence levels per change. ## Quick Start Ask the agent to refactor the module at src/booking and produce a refactor proposal without modifying any files.
