Skip to main content
skill CX Codex

legacy-modernizer · dokhacgiakhoa — Claude Code skill: refactor legacy codebases

legacy-modernizer refactors aging systems piece by piece without downtime. Routes traffic between old and new code using the Strangler Fig pattern, retiring legacy modules only when replacements are solid.

MIT 1 installs ★ 513 updated 2026-06-11

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill legacy-modernizer -a claude-code
Open on GitHub

What legacy-modernizer does

legacy-modernizer breaks apart legacy monoliths and brings them up to date step by step. Tackles outdated dependencies, old frameworks (jQuery, early Angular), codebases without clear boundaries. The skill maps a strategy first: audit the code, chart a migration path, stabilize in phases.

Five internal modules cover the full journey. Strangler Fig inserts a gateway between old and new, extracts one feature at a time, decommissions legacy once the new version runs stable. Dependency upgrades happen incrementally—v1 to v2 to v3—rather than one leap. Tools like putout or jscodeshift handle syntax transformation (Class to Hooks, jQuery to vanilla JS). Framework moves (Angular to React, monolith to microservices) get their logic and state mapped cleanly. Testing uses visual regression, side-by-side production runs for a traffic sample, and a rollback plan.

The standard cycle runs: technical audit and roadmap, stabilize critical bugs in legacy, build the new system, shadow test old versus new, cut over completely. Works without TypeScript and specialized tooling, though type checking on Java, C#, or Go requires language-specific setup.

What it helps with

  • design a modernization plan without taking the service offline
  • upgrade outdated library versions while avoiding breaking changes
  • move components from jQuery to vanilla JavaScript or React
  • extract a microservice from a monolith by isolating module boundaries
  • run new and old systems side by side, then switch traffic over

Example prompts for the agent

  • Plan a migration from Angular 1 to React using the Strangler Fig pattern for our app
  • Audit tech debt in our Django 2.2 monolith and create a roadmap to modernize dependencies
  • Convert jQuery plugins to modern JavaScript and add TypeScript types

How to install legacy-modernizer

1Skills CLI (Vercel)

npx skills add Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill legacy-modernizer -a claude-code

2Manually: put the files in place

~/.claude/skills/legacy-modernizer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/legacy-modernizer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about legacy-modernizer

How do I install legacy-modernizer in Claude Code?

Run npx skills add Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill legacy-modernizer -a claude-code, then open ~/.claude/skills/legacy-modernizer/SKILL.md. For Codex, Cursor, or Gemini CLI, change the -a flag to codex, cursor, or gemini-cli.

What does legacy-modernizer do?

It charts a modernization strategy: how to isolate modules, upgrade dependencies in the right order, grow new code alongside old without interruption, and validate changes safely.

Does this skill work for all programming languages?

The strategy patterns are language-agnostic—Strangler Fig, shadow testing, and rollback apply everywhere. Example commands target JavaScript, but the same approach translates to Java, Python, Go, or C# with tool adjustments.

Source text

SKILL.md · MIT
---
name: legacy-modernizer
description: Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization.
category: development
version: 4.1.0-fractal
layer: master-skill
---

# 🏛️ Legacy Modernizer Master Kit

You are a **Principal Modernization Engineer and Software Strategist**. You transform "Ball of Mud" architectures into clean, modern, and performant systems without braking existing business value.

---

## 📑 Internal Menu
1. [Modernization Strategy (Strangler Fig)](#1-modernization-strategy-strangler-fig)
2. [Dependency & Version Upgrades](#2-dependency--version-upgrades)
3. [Code Migration & Refactoring](#3-code-migration--refactoring)
4. [Framework Transitions (e.g., Angular to React)](#4-framework-transitions)
5. [Validation & Backward Compatibility](#5-validation--backward-compatibility)

---

## 1. Modernization Strategy (Strangler Fig)
- **Identify Borders**: Find clear service or module boundaries to extract.
- **Proxy Layer**: Use an API gateway or proxy to route traffic between the old and new systems.
- **Incremental Extraction**: Move one feature at a time, sunsetting the legacy part only when the new one is 100% stable.

---

## 2. Dependency & Version Upgrades
- **Asset Audit**: Inventory all outdated 3rd-party libraries.
- **Breaking Changes**: Review changelogs for major version jumps.
- **Step-by-Step Upgrade**: Move through intermediate versions (e.g., v1 -> v2 -> v3) instead of one giant leap.

---

## 3. Code Migration & Refactoring
- **Automated Refactoring**: Use tools like `putout` or `jscodeshift` for mass renames or syntax updates.
- **Pattern Transformation**: Convert Class components to Hooks, or jQuery to Vanilla JS.
- **Type Integration**: Incrementally add TypeScript to JS projects to ensure type safety during the build.

---

## 4. Framework Transitions
- **Angular-to-React/Vue**: Map component logic and state management.
- **Monolith-to-Microservices**: Extract domain logic into independent services.
- **SSR-to-Streaming**: Modernize data-fetching patterns for better performance.

---

## 5. Validation & Backward Compatibility
- **Visual Testing**: Use visual regression tools to ensure the UI looks identical after refactoring.
- **Side-by-Side Running**: Run both systems in production for a subset of users.
- **Rollback Strategy**: Always have a way to flip the switch back to the legacy system if something fails.

---

## 🛠️ Execution Protocol

1. **Phase 1: Technical Audit**: Quantify tech debt and build a migration roadmap.
2. **Phase 2: Core Stabilization**: Fix critical bugs in legacy before migrating.
3. **Phase 4: Extraction**: Build the new version using modern Master Skills (e.g., `modern-web-architect`).
4. **Phase 5: Shadow Testing**: Compare outputs of legacy vs. modern.
5. **Phase 6: Full Cutover**: Switch all traffic and delete legacy source code.

---
*Merged and optimized from 5 legacy modernization and migration skills.*


## 🧠 Knowledge Modules (Fractal Skills)

### 1. [strangler_fig_pattern](./sub-skills/strangler_fig_pattern.md)

© Dokhacgiakhoa · MIT · Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI

Similar skills

All skills for Code review and refactoring →

legacy-modernizer by other authors comes first.

legacy-modernizer https://github.com/Jeffallan legacy-modernizer — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that produces incremental migration plans for aging codebases. It maps dependencies and designs API facades before any production code changes. CX Codex +1 4,700installs legacy-modernizer sickn33 legacy-modernizer guides safe, incremental refactoring of legacy codebases and framework upgrades while preserving existing runtime behavior. CX Codex +1 2installs code-refactoring-legacy-modernizer Seth Hobson code-refactoring-legacy-modernizer — a subagent for Claude Code, Codex, and Cursor that moves legacy codebases forward through incremental framework migrations and technical debt paydown. CX Codex ★ 42,780repo stars legacy-modernize Seth Hobson legacy-modernize — a command for gradually updating legacy systems using the strangler fig pattern. Orchestrates specialized agents for code assessment, test coverage, and incremental component replacement without service interruption. CX Codex +1 ★ 126repo stars architecture-modernizer davila7 architecture-modernizer is a Claude Code subagent for planning monolith splits, microservices, and event-driven systems. Call it to map module boundaries and shape a modernization plan. CX Codex 1,768installs vb6-legacy Claude MPM Team vb6-legacy — a skill for maintaining Visual Basic 6 code, working with COM interop, and planning migrations to VB.NET. Contains reference patterns for VB6 support and examples of safe COM object usage from .NET. CX Codex +1 345installs modernize-brief official Anthropic modernize-brief compiles legacy analysis artifacts into a phased Modernization Brief. It organizes technical steps, sets entry criteria, and outlines build commands for review boards. CX Codex +1 ★ 47,914repo stars doc-and-modernize official github doc-and-modernize analyzes a local codebase to generate a cited architecture document and creates a phased migration plan for legacy stacks. CX Codex +1 108installs

From the same set5

Project sponsors

Companies that keep this analytics open