gitnexus-refactoring

To safely rename a function across multiple files, this Skill maps symbol dependents and execution flows, separating high-confidence graph edits from lower-confidence AST edits for careful review. It ensures interfaces, implementations, callers, and tests are updated in a controlled order to prevent breaking callers.

The best way to extract logic into a module without missing dependencies is using impact-aware restructuring. This process finds upstream and downstream dependents involving the target, helping you update interfaces, implementations, and callers in the right sequence to avoid scope surprises.

Impact analysis for splitting services works by mapping symbol relationships and planned update order across dependent code paths. It uses impact, context, and query steps to find upstream and downstream dependents, ensuring interconnected call graphs are updated safely.

Yes, you can verify code changes and run affected tests after a multi-file refactor. The Skill includes change detection verification that detects and summarizes affected files, symbols, and processes to reduce scope surprises and ensure tests are updated.

Yes, this refactoring approach works for moving code and reorganizing files with interconnected call graphs. It applies to restructuring code across an existing codebase by mapping symbol dependents and execution flows to ensure safe multi-file refactoring.

You need change detection verification when renaming classes or functions to prevent risky refactors. It detects and summarizes affected files, symbols, and processes after the refactor, reducing scope surprises and ensuring callers and tests are not silently broken.