Skip to main content
skill CX Codex

full-codebase-migrator — Claude Code skill: migration plans

The full-codebase-migrator skill examines a whole repository and turns it into a file-level migration plan. Use it for JS-to-TS work, React class conversion, or framework changes.

MIT 251 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill full-codebase-migrator -a claude-code
Open on GitHub

What full-codebase-migrator does

full-codebase-migrator collects source files, project structure, configuration, package manifests, and Git metadata. It then maps imports into a dependency graph, groups files into layers, detects cycles, and reviews each file for migration work.

The main deliverable is migration-plan.md, covering the file inventory, dependency order, per-file changes, risk assessment, effort estimates, and rollback planning. It can also write migration-plan.json when a machine-readable result is useful. The skill relies on Read, Glob, Grep, Write, Bash, and Agent.

For repositories with 500+ files, directory subtrees can be read through sub-agents. The workflow also accounts for monorepos, partially migrated projects, and codebases without tests. Effort estimates include a 20% buffer.

What it helps with

  • plan a JavaScript-to-TypeScript migration
  • convert React class components into hooks in stages
  • order file changes around dependency relationships
  • score migration risks and estimate effort
  • produce a machine-readable migration-plan.json

Example prompts for the agent

  • Review this repository and create a JavaScript-to-TypeScript migration plan.
  • Map the React class components, then plan their conversion to hooks by file.
  • Analyze src and write the result to migration-plan.md.

How to install full-codebase-migrator

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill full-codebase-migrator -a claude-code

2Manually: put the files in place

~/.claude/skills/full-codebase-migrator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/full-codebase-migrator/

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

Questions about full-codebase-migrator

How do I install full-codebase-migrator in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill full-codebase-migrator -a claude-code, then check ~/.claude/skills/full-codebase-migrator/SKILL.md.

What does full-codebase-migrator do?

It reads a codebase, maps its dependencies, and creates a staged migration plan with file-level changes, risks, effort estimates, and rollback planning.

How does full-codebase-migrator handle large repositories?

With 500+ files, it can assign directory subtrees to sub-agents for reading. Very large codebases use adjusted handling.

Source text

SKILL.md · MIT
---
name: full-codebase-migrator
description: Uses 1M context window to ingest an entire codebase and output a file-by-file migration plan. Supports JS to TS, React class to hooks, framework migrations, and more. Generates migration-plan.md with file inventory, dependency graph, migration order, file-by-file changes, estimated effort, and risk assessment.
tools: Read, Glob, Grep, Write, Bash, Agent
user_invocable: true
---

# Full Codebase Migrator

Leverage the full 1M token context window to ingest an entire codebase, understand its architecture end-to-end, and produce a comprehensive, file-by-file migration plan that a team can execute sequentially without conflicts.

## Contents

- `references/migration-types.md` -- supported migration types; when to use and when not to use this skill.
- `references/ingestion.md` -- architecture, glob patterns, metadata collection, read order, context budgeting, and dependency graph construction (Steps 0-2).
- `references/workflow-detail.md` -- per-file assessment, migration order, risk scoring, and effort estimation templates (Steps 3-6).
- `references/output-template.md` -- migration-plan.md and migration-plan.json templates, edge cases, and the final quality checklist (Steps 7-8).

## Workflow

1. Identify scope. Determine migration type, scope (full repo or directory), output location for migration-plan.md, and any exclusions or constraints. Infer from the user's prompt when already specified. See `references/migration-types.md` for supported types and fit.
2. Ingest the codebase. Glob all source files, collect metadata with Bash (line counts, package manifest, configs, git history, directory tree), then Read every source file. For 500+ file codebases, dispatch Agent sub-agents to read directory subtrees in parallel. See `references/ingestion.md`.
3. Build the dependency graph. Extract every import, build an adjacency list, classify each file into layers, detect circular dependencies, and classify external dependencies. See `references/ingestion.md`.
4. Assess each file. Produce a per-file migration assessment covering layer, complexity, patterns found, required changes, prerequisite dependencies, risk factors, and testing impact. See `references/workflow-detail.md`.
5. Calculate migration order. Run a topological sort by layer, apply practical adjustments (quick wins, high-risk-early, break cycles first), and group files into buildable, PR-sized phases. See `references/workflow-detail.md`.
6. Assess risk. Score each file 1-5 on complexity, centrality, volatility, test coverage, and external coupling. Build the migration-level risk matrix and rollback strategy. See `references/workflow-detail.md`.
7. Estimate effort. Derive per-file, per-phase, and total estimates with overhead and a 20% buffer, then translate into calendar time by team size. See `references/workflow-detail.md` and the effort calibration table in `references/migration-types.md`.
8. Generate the deliverable. Write migration-plan.md to the output location, and migration-plan.json when machine-readability helps. Verify against the quality checklist before delivering. See `references/output-template.md`.

## Edge Cases

Codebases too large for context, monorepos, partially migrated codebases, and codebases without tests each need adjusted handling. See `references/output-template.md`.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set185

The whole set →
investor-update-writer investor-update-writer generates monthly and quarterly updates for startup investors into a structured investor-update.md file using metrics, milestones, and runway. CX Codex +1 252installs onboarding-checklist Generates phased client onboarding checklists in onboarding-checklist.md with task ownership, criteria, and five email templates for SaaS, agencies, or consulting. CX Codex +1 251installs multi-agent-client-onboarding multi-agent-client-onboarding runs three parallel agents to audit workflows, map a client’s tech stack, and draft an AI roadmap. It is built for structured client assessments. CX Codex +1 251installs market-sizing Calculates TAM, SAM, and SOM for business plans and investor decks. Researches industry data online and writes a detailed market-sizing.md report. CX Codex +1 251installs competitor-intel-agent competitor-intel-agent monitors competitor sites, pricing models, hiring shifts, and product releases while saving snapshot history. CX Codex +1 251installs okr-generator okr-generator builds a structured okr-plan.md file using the Google and Intel framework from your company targets and team baselines. CX Codex +1 250installs renewal-predictor The renewal-predictor skill analyzes seven account health dimensions—engagement, support, adoption, satisfaction, billing, stakeholder continuity. CX Codex +1 249installs utm-link-generator utm-link-generator builds UTM-tagged links under unified naming rules, tracks duplicates, and outputs variants for LinkedIn, email, social, and ads. CX Codex +1 249installs

Project sponsors

Companies that keep this analytics open