What problem does it solve? Refactoring code across a large codebase is risky because it is hard to know every caller and dependent of a symbol before renaming, extracting, or moving it. This Skill uses the GitNexus code graph to map the full blast radius of a change before applying it, preventing broken callers and missed references. ## Core Features & Use Cases - Safe Symbol Renaming: Preview and apply multi-file renames with gitnexus_rename, distinguishing high-confidence graph edits from lower-confidence ast_search matches that need review. - Impact Analysis: Use gitnexus_impact and gitnexus_context to map all upstream dependents and incoming/outgoing references before extracting modules or splitting services. - Change Verification: Run gitnexus_detect_changes after refactoring to confirm only expected files changed and identify affected execution flows and risk level. - Use Case: You need to rename validateUser to authenticateUser across the codebase. The Skill verifies the index is fresh, previews 12 edits across 8 files, flags a dynamic reference in config.json for manual review, applies the rename, and confirms the affected LoginFlow and TokenRefresh processes so you know which tests to run. ## Quick Start Ask the assistant to rename a function safely across the codebase using GitNexus, for example: rename validateUser to authenticateUser and show me all affected files first.
