domains / families / software-engineering / refactor-clean

refactor-clean

separate

Refactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.

When to use

• rename requests
• stale or misleading names
• legacy leftovers
• changed scope
• duplicated concepts
• local adapters
• obsolete owners
• over-large module

When not to use

• adding compatibility layers beside problems
• layering sediment
• tacking on features without refactoring

Skill page

Source