Refactoring — structured improvement without behavior change

What I do

• Detect code smells: long methods, duplicate code, large classes, feature envy, primitive obsession, and switch/if-else chains
• Produce a phased refactoring plan that preserves existing behavior
• Recommend applicable patterns for each problem area
• Define rollout steps, risk mitigations, and measurable success criteria

When to use me

Activate this skill when:

• Code shows duplication, high complexity, or poor separation of concerns
• A module or class has grown too large to maintain safely
• You need a safe, test-first improvement roadmap before touching production code
• Any request containing "refactor", "clean up", "reduce complexity", "restructure", "break apart", or "eliminate duplication"