What problem does it solve? Refactoring code without understanding dependencies risks breaking critical paths and leaving dead code behind. This Skill uses a knowledge graph to analyze impact before changes are applied, so renames and restructuring happen with full visibility into affected locations. ## Core Features & Use Cases - Refactoring Suggestions: Use refactor_tool in suggest mode to get community-driven refactoring recommendations and dead_code mode to find unreferenced code. - Safe Renames: Preview every affected location with rename mode, then apply changes via apply_refactor_tool using the returned refactor_id. - Impact Verification: Check get_impact_radius and get_affected_flows before major refactors, then run detect_changes afterward to confirm the blast radius. - Use Case: Before renaming a core utility function used across services, preview all call sites, verify no critical flows break, apply the rename, and validate the change impact in under five tool calls. ## Quick Start Ask the assistant to safely rename a function across the codebase and verify that no critical flows are affected.
