rewrite
Installation
SKILL.md
Summary
Use this skill to plan and execute a deliberate, well-documented, and risk-aware full rewrite of a codebase or package. Rewrites are opinionated and may break APIs, repository layout, or deploy-time contracts; they are appropriate when technical debt, architecture constraints, or product direction make incremental refactors impractical.
When to use
- The team has decided a behavior-preserving refactor is insufficient.
- The repository suffers from pervasive architectural issues or unfixable legacy constraints.
- Backward compatibility may be broken but migration paths are acceptable.
- A new target architecture, platform, or runtime is required (e.g., move from monolith → services, Python2 → Python3+, callback → async).
- The user explicitly requests a "clean start" and accepts migration work.
When not to use
Related skills