What problem does it solve? Refactoring code across a large codebase is risky because renaming a symbol 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 verified rather than guessed. ## 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 ast_search matches that need review. - Impact Analysis Before Changes: Map all upstream dependents and affected execution flows before extracting modules, splitting services, or moving code. - Post-Refactor Verification: Run change detection to confirm only expected files changed and identify which processes need test coverage. - Use Case: You need to rename validateUser to authenticateUser across 8 files including a dynamic reference in config.json. The Skill previews all 12 edits, flags the risky dynamic reference for review, applies the changes, and tells you to run tests for the LoginFlow and TokenRefresh processes. ## Quick Start Ask the AI to safely rename a function across the entire codebase, previewing all affected files and dependents before applying any changes.
