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 discipline where verification is established before edits and re-run after, so refactoring never silently changes behavior. ## Core Features & Use Cases - Behavior-Preservation Boundary: Defines what must stay unchanged—public interfaces, failure behavior, ordering, and compatibility—before any structural edit begins. - Incremental Ownership Moves: Moves one ownership boundary at a time, keeping every intermediate state buildable and testable. - Scope Discipline: Keeps feature changes, dependency growth, and configuration changes out of the refactor unless explicitly scoped. - Use Case: When splitting a monolithic module into separate packages, use this Skill to extract one component at a time, running the same test suite before and after each move to confirm identical behavior. ## Quick Start Use safe-refactor to extract this module into its own package while keeping all existing tests passing.
