Legacy Modernizer guides Claude through a migration in five steps: assess the system, plan an incremental roadmap with rollback triggers, build a safety net of tests, migrate behind a facade and feature flags, and validate before the old code is retired. Each step ends with a validation checkpoint, such as traffic moving 5, 25, 50 and then 100 percent while error rates stay within baseline.
Five reference files cover the strangler fig pattern, refactoring patterns, migration strategies, legacy testing and system assessment.
What You Get
- An assessment with a dependency map, risk register and technical debt estimate
- A phased migration plan with a rollback trigger and owner for each phase
- Characterization, golden master, snapshot, parallel-run and property-based tests for existing behavior
- Facades, adapters and feature-flag routing for gradual traffic shifts
- Strategies for database dual writes, expand and contract schema changes, API versioning, framework and language upgrades
- Monitoring and alert suggestions for each rollout step
Common Use Cases
- Replacing a monolith piece by piece with the strangler fig pattern
- Adding tests around code nobody understands before changing it
- Migrating a database with dual writes and a staged cutover
- Moving a Flask service to FastAPI behind a routing proxy
- Extracting a payment or inventory service from a monolith
- Upgrading a Python 2 codebase to Python 3 in steps
What Makes It Unique
The skill forbids big-bang rewrites and makes every phase carry a rollback plan. Tests come before any change, and a gradual traffic ramp with error and latency thresholds decides when the legacy path may go. Its references include parallel-run testing and mutation testing for legacy code, and a stakeholder communication template.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. It tells the agent to run the characterization test suite and the full test suite, so it uses the shell, and it writes facades, adapters, tests and migration code. The assessment reference includes a script that calls subprocess to analyze the codebase, and the testing reference installs a mutation testing package with pip. Examples read feature flags from environment variables, and the framework migration example proxies requests to a local service. The skill does not fetch web pages or call outside APIs.