What problem does it solve? Structural code changes like extractions, consolidations, and ownership moves often introduce subtle regressions because behavior verification is skipped or done inconsistently. This Skill enforces a disciplined refactoring workflow where verification brackets every structural edit. ## Core Features & Use Cases - Behavior-Preservation Boundary: Defines the scope of what must stay unchanged—public interfaces, failure behavior, ordering, and compatibility—before any edit begins. - Incremental Ownership Moves: Moves one ownership boundary at a time while keeping every intermediate state buildable and testable. - Verification Bracketing: Runs the same proof before and after the change, stopping only when behavior matches and the requested structure is achieved. - Use Case: When extracting a shared module from a monolith, use this Skill to keep feature changes out of the refactor, preserve the public API, and confirm tests pass identically at each step. ## Quick Start Use safe-refactor to extract this duplicated logic into a shared module while preserving existing behavior and keeping tests green.
