refactoring-specialist

To modularize a large codebase safely, you must establish baseline tests, plan module extraction moves, make atomic commits, and verify the full test suite to ensure no behavior change occurs during the structural transformation.

Fixing circular dependencies and god objects requires applying dependency inversion and cross-file restructuring. This decomposes oversized modules into clearer interfaces, reducing coupling while preserving the original execution behavior.

Decomposing large modules to reduce shotgun surgery and feature envy involves extracting distinct interfaces and moving behaviors to appropriate modules. This restructuring simplifies the codebase and localizes changes without altering functionality.

Refactoring complex code without a baseline test suite is highly discouraged. Baseline tests are a required step in the process to verify behavior preservation and ensure the structural design improvements do not introduce regressions.

Structural code transformation requires strict adherence to atomic commits and continuous test verification. If the tightly coupled code lacks sufficient test coverage, safely performing module extraction and dependency inversion becomes significantly limited.