full-codebase-migrator

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.

Ir para a instalação

Repositório: OneWave-AI/claude-skills
Última atividade na origem: 8 de junho de 2026 às 01:17
Idioma detectado do SKILL.md: inglês
Estrelas: 256
Forks: 42

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/OneWave-AI/claude-skills --skill full-codebase-migrator

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

5 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

design-export-repair

Fixes broken decks/PDFs exported from Claude's "Design" feature (or similar AI deck generators) — cut-off or clipped text, wrong/substituted fonts, and corrupted .pptx package structure that shows up only once you export to PDF, not while looking at it in the app. Use this skill whenever the user uploads a zip, .pptx, or .pdf exported from Claude Design (or mentions "Design" export, an AI-generated deck, or a generated slide deck/PDF) AND reports it looking broken, wrong, cut off, garbled, or different from the original when opened, printed, or converted to PDF — even if they don't use the word "repair" or name the specific defect. Also trigger for general "my exported PDF/deck is broken, help fix it" requests when the file was clearly produced by an AI design/deck tool rather than hand-authored. Produces both a repaired, still-editable .pptx and a clean PDF, plus a report of exactly what was wrong and what changed.

2026-08-10

cash-flow-forecaster

Build a 13-week rolling cash flow forecast from bank exports, AR aging, AP bills, payroll, and recurring commitments -- the report that tells a small business whether it survives the quarter. Flags the crunch weeks early enough to act.

2026-07-15

commercial-lease-analyzer

Decode a commercial lease before signing or renewing -- true all-in occupancy cost (base rent plus NNN/CAM plus escalations), the clauses that hurt small tenants (personal guarantees, relocation, restoration), and the negotiation asks landlords routinely grant. The lease is most SMBs' biggest fixed cost and least-read document.

2026-07-15

Ver todas deste repositório

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

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.

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.

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.

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.

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.

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.

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.

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.