refactor-optimizer

To refactor code without breaking passing tests, apply systematic changes iteratively and run the full test suite after each modification. If any test fails, revert the change immediately to preserve the green test state and ensure no regressions are introduced.

Cleaning up code after a minimal TDD implementation involves iteratively improving readability, applying SOLID principles, and removing duplication. Extract magic numbers, clarify naming, and optimize queries while continuously running tests to validate each refactoring step.

Yes, you can optimize database queries and batch operations during a refactor cycle. Identify performance bottlenecks in hot paths and apply measured improvements to reduce query overhead, while ensuring the test suite remains green after each optimization change.

This refactoring approach works directly with feature branches and iterative cycles. You apply it to finished minimal implementations on feature branches, progressively reducing technical debt and improving clarity through repeated, test-validated refactoring passes.

You should extract classes or services to align with SOLID principles when module responsibilities grow beyond a single concern. Restructure the code to follow project patterns, ensuring architecture alignment and maintainability while keeping tests green.

Code refactoring requires running tests after every single change to guarantee that structural improvements do not introduce regressions. This test-driven safety net allows you to confidently apply DRY principles and readability enhancements, reverting immediately if failures occur.