refactor

Invoke the refactor skill on the target file. It writes characterization tests that pin down current behavior, confirms they pass on the pre-change code, then performs the extraction or split and re-verifies tests, callers, and code quality before committing.

The skill auto-detects god classes over 600 lines with 5+ responsibilities and escalates to an iterative decomposition protocol. It extracts one responsibility at a time, runs tests after each extraction, and checks size gates until the original file has a single responsibility.

Yes. Each run writes a versioned contract file under zuvo/contracts recording its phase and evidence. Passing the continue argument resumes the contract at its recorded stage instead of restarting analysis.

Yes, in degraded mode. When CodeSift is unavailable, agents fall back to Read, Grep, and Glob for dependency mapping and duplicate detection, and the run records the degradation explicitly rather than claiming full verification.

The skill routes to CHARACTERIZE_GAP mode and blocks production edits until pin-down tests exercise every uncovered unit and pass on the old code. Mutation probes then confirm the tests actually fail when behavior changes.

Use refactor only for structural changes that preserve behavior, such as renames, extractions, splits, and deduplication. New features or behavior changes belong to a build-oriented skill, since refactor's gates are designed to prove nothing observable changed.