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, tests, and dynamic references scattered across many files. This Skill uses GitNexus's dependency graph and impact analysis to map every dependent before making changes, so refactoring is planned and verified rather than guesswork. ## Core Features & Use Cases - Impact-First Planning: Maps all upstream dependents and affected execution flows with gitnexus_impact before touching any code. - Automated Multi-File Rename: Previews and applies symbol renames across files with gitnexus_rename, distinguishing high-confidence graph edits from ast_search edits that need manual review. - Post-Change Verification: Uses gitnexus_detect_changes to confirm only expected files changed and to assess the risk level of affected processes. - Use Case: When renaming a function like validateUser to authenticateUser, the Skill previews 12 edits across 8 files, flags a dynamic reference in config.json for review, applies the edits, then verifies the affected LoginFlow and TokenRefresh processes so you know which tests to run. ## Quick Start Ask the AI to safely rename a function or extract a module, for example: "Rename the validateUser function to authenticateUser and update all its callers."
