refactor-assist

To refactor legacy code incrementally while preserving behavior, you identify opportunities across modules and apply proven patterns like extract function or decompose large classes in small, validated steps. This ensures functionality remains unchanged throughout the modification process.

The best way to decompose large classes in a multi-file codebase is through incremental pattern application. You apply targeted refactoring patterns across modules step by step, using validation checks to ensure behavior remains unchanged throughout the structural improvements.

Yes, you can replace conditional logic with polymorphism without breaking functionality by using behavior-preserving refactoring techniques. This involves applying the pattern incrementally and running validation checks to verify the modified code matches the original operational outcomes.

Identifying refactoring opportunities across multiple modules involves analyzing the codebase for patterns like dead code, large classes, or complex conditionals. You provide a target module and goal, then receive guidance on safe, incremental improvements with behavior preservation checks.

Yes, incremental refactoring works for multi-file codebases needing regression-safe improvements. It supports applying patterns across modules with built-in validation checks to ensure behavior remains unchanged, making it suitable for complex structural modifications.

You should avoid incremental refactoring when you cannot establish baseline behavior validation checks. Without the ability to verify that functionality remains unchanged after each step, applying structural patterns like extract function or introduce parameter object risks introducing regressions.