What problem does it solve? Refactoring code across a large codebase is risky because renaming a symbol or moving a module can silently break callers, tests, and dynamic references scattered across many files. This Skill uses the GitNexus code graph to map every dependency before making changes, so refactors are applied with full visibility into their impact. ## 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 Before Changes: Map all upstream dependents and affected execution flows before extracting modules, splitting services, or moving code. - Post-Refactor Verification: Detect which files, symbols, and processes changed after refactoring and assess the risk level to know which tests to run. - Use Case: You need to rename validateUser to authenticateUser across a TypeScript project. The Skill previews 12 edits across 8 files, flags a dynamic reference in a config file for manual review, applies the changes, and tells you which login flows to retest. ## Quick Start Ask the assistant to rename a function safely across the entire codebase using GitNexus impact analysis and dry-run preview.
