gitnexus-refactoring

To safely rename a function across multiple files, you must map all dependents and execution flows before making changes. This skill provides impact analysis and change detection tools to verify only expected files are affected, reducing the risk of breaking dependencies during code refactoring.

Impact analysis for code refactoring is the process of mapping all dependents and execution flows before modifying symbols. It identifies potential risks by detecting changes and verifying that only expected files are affected, ensuring precise restructuring without introducing bugs.

To perform a dry run before renaming code symbols, execute the command `gitnexus_rename({symbol_name: "oldName", new_name: "newName", dry_run: true})`. This simulates the refactoring operation to verify the expected impact without modifying the actual codebase.

Yes, you need gitnexus installed because this refactoring workflow requires gitnexus tools to perform impact analysis, dependency mapping, and symbol renaming. The skill relies on these underlying tools to provide context and change detection during code restructuring.

The best way to extract modules or split functions without breaking dependencies is to use a workflow that maps all dependents and execution flows beforehand. This approach provides the necessary context and change detection tools to verify only expected files are affected during restructuring.