Skip to content
SkillModel-led1,145 tokens in use

Legacy Modernizer

Plans and runs incremental migrations of aging codebases with the strangler fig pattern, branch by abstraction, characterization tests and feature flags.

12,471 stars on the repository MIT LicenseJeffallan/claude-skills · skills/legacy-modernizer
/plugin marketplace add jeffallan/claude-skills /plugin install fullstack-dev-skills@fullstack-dev-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Legacy Modernizer costs

70tokens idle
1,145tokens in use
14,176tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter15/15
  • Structure22/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity36
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers