What problem does it solve? Codebases accumulate duplication, dead code, wrong-sized abstractions, and logic bugs that surface only after they cause damage. This Skill performs a rigorous, read-only audit of named files or components and turns what it finds into a prioritized, evidence-backed plan you approve before any code changes. ## Core Features & Use Cases - Six structured detections: duplicated logic and values, dead code, wrong-sized abstractions, logic bugs, and cost/boundary issues, each requiring file:line evidence and a concrete failure scenario. - Neighbourhood mapping: traces importers, shared constants, contracts, and sibling components beyond the named targets, since duplicates by definition live in files you were not given. - Severity-labelled plan output: findings are ranked Critical through FYI, each with a proposed remedy and consumer count, then written into a refact plan doc that is red-teamed before you see it. - Use Case: Point it at two overlapping modules before building on them; it proves which copy should survive, flags an unenforced schema cap, and delivers a sequenced fix plan without editing a single line of code. ## Quick Start Ask the agent to run /inspect on the specific files or components you want audited, for example: run /inspect on src/stores/session.ts and src/api/auth.ts.