refactor

Code refactoring requires mapping architecture before and after, tracing dependencies, and defining a behavior preservation strategy. You produce an explicit affected-file list and a zero-fog checklist to verify no functionality changes during the refactor.

Risk assessment for legacy module refactoring involves classifying behavior-preservation risks, surfacing hidden complexity, and identifying integration points. You trace dependencies across the architecture to map exact scope and prescribe required tests for affected files.

This refactoring approach applies to both component-level and cross-module refactors. It handles architecture mapping and dependency tracing across module boundaries, ensuring behavior preservation and test strategy coverage for complex, multi-file integration points.

Scoping brittle module boundaries requires restating goals, asking clarifying questions, and challenging assumptions. You map the exact refactor scope, compare refactoring options, sketch tradeoffs, and list unknowns to spike before implementation.

A refactoring test strategy classifies behavior-preservation risks and prescribes specific tests for affected files and integration points. You produce a concrete implementation plan naming files, identifying test coverage requirements, and listing unknowns to spike.

Dependency tracing in refactoring plans surfaces hidden complexity and maps architecture before and after changes. It identifies integration points across module boundaries, ensuring your affected-file list accurately captures all behavior-preservation risks and required tests.