What problem does it solve?
This Skill eliminates the risk of breaking production code during unstructured refactoring, provides access to Martin Fowler's proven refactoring catalog, and removes guesswork about when refactoring is safe versus when a full rewrite is the better choice.
Core Features & Use Cases
- Proven Refactoring Catalog: Full Martin Fowler pattern library with before/after code examples in Java, Kotlin, and Python for common structural improvements like extract method, rename, and move patterns.
- Large-Scale Migration Patterns: Strangler Fig, Branch by Abstraction, and Parallel Change (Expand-Contract) for safely modernizing legacy systems without service downtime.
- Safe Refactoring Discipline: Pre-refactor checklists, anti-pattern avoidance guidance, and clear rules for when to refactor versus when to rewrite to avoid wasted effort.
- Use Case Example: If you're maintaining a legacy Python service with tangled business logic, use this Skill to safely extract methods, replace conditional dispatch with polymorphism, and incrementally improve code maintainability without breaking existing functionality.
Quick Start
Use the refactoring-patterns skill to safely extract the calculateTotal method from the printBill function in your order processing service, following the provided before/after examples to preserve existing behavior.