refactoring-methodology

To refactor recently modified files without changing behavior, identify touched modules and run a proportionate pass to extract reusable helpers, evaluate duplication, and reduce structural debt. The methodology enforces mandatory checks for size, readability, testability, and integration gaps with explicit guardrails.

A proactive refactoring pass is a workflow that hunts for extraction opportunities, duplication, and oversized functions in touched files and nearby code areas. Apply it when recently modified code exposes structural debt or integration gaps that need behavior-preserving improvements.

Yes, this refactoring methodology explicitly checks for integration gaps, testability, readability, and code duplication. It applies mandatory checks across the touched area to ensure architecture rules are respected and behavior remains preserved during structural improvements.

You should not use a behavior-preserving refactor playbook for adversarial defect review or net-new feature implementation. It is strictly designed for evaluating and improving existing code structure, extracting reusable helpers, and reducing duplication in already touched files.

To evaluate overly large functions and structural debt, apply a repeatable analysis flow that inspects touched files and neighboring code areas. This methodology uses mandatory size, duplication, readability, and testability checks to identify extraction opportunities while preserving intended behavior.