gitnexus-refactoring

Blast-radius analysis maps dependents and affected modules before executing refactors. It reveals how changes ripple across interdependent components, reducing risk and manual rework during symbol renames, module extractions, splits, or file moves.

The recommended update order for safe refactoring is interfaces, then implementations, followed by callers, and finally tests. This sequencing prevents breaking changes by updating dependencies systematically from foundational definitions outward.

Use context queries to inspect incoming and outgoing references for a symbol. This reviews how the symbol is used across the codebase, ensuring all affected areas are captured before proceeding with file moves or splits.

Yes, refactors can be planned across multiple interdependent components simultaneously. Dependency mapping coordinates changes across the entire codebase, ensuring splits and moves are tracked comprehensively rather than in isolation.

Running impact analysis when the index is stale ensures accurate dependency mapping. A stale index may miss recently modified references, leading to incomplete blast-radius calculations and unsafe refactor execution.