Software EngineeringEngineeringPlatinum

Improve old code without changing its behavior.

Refactoring Pattern Guide

Refactoring, Legacy Code, Testing

1 loadsintermediatev6.0

Best for

▸Legacy codebase cleanup with safe, incremental refactoring patterns
▸Code smell identification and systematic elimination using Fowler's catalog
▸Test-first refactoring of untested production code using Feathers' techniques
▸Design pattern extraction from procedural code through proven transformations

What you'll get

▸Named code smell identification (Long Method, Feature Envy, etc.) with specific line references and impact assessment
▸Detailed refactoring mechanics with before/after code examples, test requirements, and rollback strategies
▸Incremental transformation plan with checkpoints, seam identification, and dependency-breaking techniques for legacy code

Expects

Specific code samples with context about the codebase, existing tests, and particular code smells or design issues to address.

Returns

Step-by-step refactoring plan with named patterns, safety checkpoints, test requirements, and incremental transformation steps that preserve behavior.

What's inside

“You are a Refactoring Specialist. You identify code smells, select behavior-preserving transformations, and produce incremental, test-backed refactoring plans for any codebase. - **Smell-first, pattern-second.** You name every smell using Fowler's exact taxonomy (Long Method, Feature Envy, Shotgun S...”

Covers

What You Do DifferentlyMethodologyWatch For

Not designed for ↓

×Complete system rewrites or architectural overhauls
×Performance optimization without behavior preservation guarantees
×Adding new features while refactoring existing code
×Refactoring without existing test coverage or seam identification

SupaScore

90.98▼

Research Quality (15%)

9.25

Prompt Engineering (25%)

9.15

Practical Utility (15%)

8.85

Completeness (10%)

9.5

User Satisfaction (20%)

9.05

Decision Usefulness (15%)

8.9

Evidence Policy

Standard: no explicit evidence policy.

refactoringcode-smellsclean-codelegacy-codedesign-patternstestingmartin-fowlersoftware-craftsmanshipcode-quality

Research Foundation: 6 sources (2 industry frameworks, 2 expert knowledge, 2 community practice)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.