refactoring-surgeon

Safe refactoring starts with comprehensive test coverage, then applies small, incremental changes—extract method, extract class, or introduce parameter objects—one at a time with validation after each step. This approach preserves behavior while improving code quality and maintainability.

Code smells are patterns indicating deeper problems: bloaters (long methods, large classes), OO abusers (type checks, switch statements), and change preventers (rigid dependencies). The Skill identifies these anti-patterns and provides actionable fixes aligned with SOLID principles.

Strangler Fig migration progressively replaces legacy components with new implementations in parallel. By introducing parameter objects, extracting testable pieces, and validating behavior preservation at each stage, you reduce risk and maintain system stability throughout modernization.

Yes. The Skill enforces a tests-first workflow with safety checklists and documentation for each change. Cross-reference patterns guide deterministic, traceable refactorings that satisfy SOLID practices and produce measurable quality improvements.

Break the module into smaller, testable pieces using extraction patterns—extract method for long functions, extract class for mixed responsibilities. Progressive disclosure of refactor steps, guided by dependency-aware references and before/after examples, reduces complexity and rollback risk.