What problem does it solve? Renaming, moving, or deleting code without knowing every affected call site leads to broken references, silently deleted live code, and failures misattributed to the refactor. This Skill enforces a preview-apply-verify discipline so every affected location is known before the first edit. ## Core Features & Use Cases - Complete reference enumeration: Builds the full edit list via code-graph rename-preview tools, IDE rename-refactoring, or grep-based baselines before any change is applied. - Blast-radius and dead-code checks: Traces callers toward entry points, flags auth/payment/public-API exposure, and verifies zero reachable callers (including dynamic dispatch) before removals. - Test-bracketed application: Runs the project's test command before and after applying, so pre-existing failures cannot be mistaken for regressions. - Use Case: Before renaming a shared utility function used across a codebase, generate the complete edit list, confirm no critical path is affected, apply the previewed refactor, and verify with test runs on both sides. ## Quick Start Ask the agent to preview renaming a function everywhere it is used, check its blast radius, then apply the change and run the test suite before and after.
