onewave-ai/full-codebase-migrator
full-codebase-migrator/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add onewave-ai/claude-skills full-codebase-migratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 8, 2026, 5:14 AM15.5s5 files scanned
SKILL.md
- 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
- 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.mdfor 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.mdand the effort calibration table inreferences/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.
Related Skills
onewave-ai/gmail-to-crm-pipeline
tools
VerifiedTrustedCommunity
Uses MCP Connectors to read Gmail inbound leads, score them by ICP fit, draft personalized responses, and log qualified leads to your CRM. Turns your inbox into an automated pipeline.
172SKILL.mdUpdated Jun 5, 2026
onewave-ai/financial-document-parser
development
VerifiedTrustedCommunity
Extract and analyze data from invoices, receipts, bank statements, and financial documents. Categorize expenses, track recurring charges, and generate expense reports. Use when user provides financial PDFs or images.
172SKILL.mdUpdated Jun 5, 2026
onewave-ai/expansion-revenue-finder
tools
VerifiedTrustedCommunity
Identifies upsell and cross-sell opportunities within existing customer accounts. Analyzes product usage, feature gaps, team growth, industry benchmarks, and competitive pressure to surface revenue expansion plays scored by potential, effort, and likelihood. Generates an expansion-playbook.md with account-by-account opportunities, recommended pitch, timing, and approach.
172SKILL.mdUpdated Jun 5, 2026
onewave-ai/executive-dashboard-generator
development
VerifiedTrustedCommunity
Transform raw data from CSVs, Google Sheets, or databases into executive-ready reports with visualizations, key metrics, trend analysis, and actionable recommendations. Creates data-driven narratives for leadership. Use when users need to turn spreadsheets into executive summaries or board reports.
172SKILL.mdUpdated Jun 5, 2026