refactor-smell

# Refactor Smell ## When to use Invoke this skill when reviewing code that is hard to read, duplicated, or risky to change. ## Steps 1. Name the smell: duplication, long method, god class, primitive obsession, shotgun surgery. 2. Confirm there are tests; if not, add a characterization test first. 3. Apply the smallest safe transform (extract, rename, move, replace conditional). 4. Keep behaviour identical; verify with the test suite after each step. 5. Stop when the code is clear; do not gold-plate or rewrite working logic. ## Examples - "Refactor this 200-line function" - "Remove duplication between these two modules" ## References Refactor in small, committable steps with passing tests between each; never mix behavioural change with restructuring in one edit.