What problem does it solve? Refactoring code across a large codebase is risky: renaming a function or extracting a module can silently break callers, dynamic references, and tests scattered across many files. This Skill uses GitNexus's code graph to map every dependency before making changes, so refactors are planned, previewed, and verified. ## Core Features & Use Cases - Automated Multi-File Rename: Preview and apply symbol renames across all files with confidence-scored edits, distinguishing graph-based edits from text-search matches that need review. - Impact Analysis: Map all upstream dependents and affected execution flows before extracting modules or splitting services. - Change Verification: Run detect_changes after refactoring to confirm only expected files changed and assess risk level for affected processes. - Use Case: Rename validateUser to authenticateUser across 8 files with a dry-run preview, review dynamic references in config files, apply the edits, then verify the affected LoginFlow and TokenRefresh processes. ## Quick Start Ask the agent to rename a function safely across the entire codebase and verify which execution flows are affected.
