What problem does it solve? Restructuring code without a safety net risks silently changing behavior or adding speculative complexity. This Skill enforces a disciplined refactoring workflow that keeps every change behavior-preserving, evidence-backed, and proportionate to the actual need. ## Core Features & Use Cases - Baseline Discipline: Establishes a verified, recoverable baseline after GREEN in a TDD cycle before any restructuring, with commits only on explicit user approval. - Priority Classification: Triages findings into Critical, High, Nice, and Skip categories so only worthwhile refactors are applied. - DRY and Speculation Guards: Distinguishes semantic duplication from structural similarity and blocks speculative abstractions or untested new behavior. - Use Case: After making a failing test pass, ask the assistant to assess the touched code; it extracts magic numbers, clarifies names, keeps tests green, and defers mutation testing to the pre-PR gate. ## Quick Start Ask the assistant to assess and refactor the code you just made pass its tests, keeping all behavior unchanged.
