What problem does it solve? Code that works but has the wrong shape — god classes, duplication, deep nesting, long methods — is risky to change because restructuring can silently break behavior. This Skill enforces a disciplined refactoring workflow where every structural move is guarded by a passing test baseline and committed independently. ## Core Features & Use Cases - Smell identification: Names the exact structural problem (god class, long method, duplicate code, primitive obsession, shallow module, and more) before any change, keeping scope to one smell per session. - Test-guarded micro-commits: Establishes a passing test baseline first, then applies one structural move per commit — extract, inline, rename, move, collapse nesting — with tests re-run after every move. - Zero new behavior enforcement: Hard rule against mixing refactoring with features or bug fixes; any behavior change is routed to a separate lane and commit. - Use Case: You inherit a 400-line method with nested conditionals. The Skill verifies test coverage exists, runs the baseline suite, then guides you through extract-method and collapse-nesting moves, each independently revertable. ## Quick Start Ask the AI to refactor the god class in your payment module using the refactoring skill, keeping all existing tests green with one move per commit.
