Semantic-Safe Change

Make code changes that preserve behavioral semantics — whether replacing an implementation, moving a module boundary, or migrating technology. This skill is a Pipeline + Reviewer that selects the correct variant based on what is changing.

Use When

Use when the user asks to:

• rewrite or replace an implementation while keeping the public surface stable
• move a module to a new package, path, or ownership boundary without breaking callers
• upgrade a framework, runtime, library version, or switch technology while preserving behavior
• extract, consolidate, or restructure code where behavior must survive the change

Do not use for: