refactoring-catalog

Safe refactoring requires applying test-backed patterns like Extract Function or Replace Conditional, running tests after each change, and committing refactorings as isolated steps to prevent regressions. A safety checklist accompanies each catalog pattern.

Common refactoring patterns include Extract Function, Rename, Move Function, and Replace Conditional. These patterns target tangled code areas to improve readability and structure while preserving existing runtime behavior.

Identify a tangled area, ensure behavior tests exist or write them, select a pattern from the refactoring catalog, apply the before/after transformation, run tests to confirm behavior, and commit as an isolated step.

Yes, tests must exist or be written for the behavior before applying refactoring patterns. The catalog explicitly requires running tests after each change to guard against regressions in production-grade codebases.

Use Replace Conditional when facing complex conditional logic that hinders readability and maintenance. The catalog provides before/after examples and safety checks to ensure the refactoring preserves runtime behavior without introducing regressions.