gitnexus-refactoring

Module extraction involves separating code into new modules while updating all existing imports and dependencies. This Skill automates the extraction workflow by applying graph-based impact analysis to identify affected references and rewrite them safely.

Dependency-aware impact analysis maps all dependents and execution flows for planned code changes before they are applied. It ensures correctness during refactoring tasks like symbol renames and file relocations by identifying every reference that needs updating.

Automating file relocations requires rewriting imports and interfaces to maintain software behavior. This Skill applies graph-based impact analysis to plan dependency-aware updates, ensuring all references are safely rewritten during the relocation process.

Yes, this approach is designed for multi-file software projects requiring dependency-aware updates. It handles large-scale refactors by generating automated change plans and utilizing graph-based impact analysis to ensure safety and correctness across the codebase.

The best way to plan a safe refactor is to run an impact analysis mapping all dependents, then review the generated change plan and import rewrites. This Skill provides checklists and templates for common scenarios to verify correctness before applying updates.

Graph-based analysis is needed for module splits to map complex execution flows and dependency chains accurately. It ensures that extracting or moving symbols does not break existing behavior by identifying all required import and reference rewrites.