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 the GitNexus code graph to map every dependent before editing, preview changes safely, and verify the affected scope afterward. ## Core Features & Use Cases - Safe Multi-File Rename: Preview all edits with dry-run mode, distinguishing high-confidence graph edits from text-search matches that need manual review, then apply across files. - Impact Analysis Before Changes: Map all upstream dependents and affected execution flows before extracting modules or splitting services. - Post-Refactor Verification: Run change detection to confirm only expected files changed and get a risk rating for affected processes. - Use Case: You need to rename validateUser to authenticateUser across a monorepo. The Skill binds the correct repository, previews 12 edits across 8 files, flags a dynamic reference in config.json for review, applies the rename, and verifies that only the LoginFlow and TokenRefresh processes are affected. ## Quick Start Ask the AI to safely rename a function across the repository, previewing all affected files before applying any changes.
