Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsCodebase Migration Planner Pro
Architects and generates technical migration plans with dependency mapping, risk registries, and rollback strategies.
$9.99
Codebase Migration Planner Pro
Example session with this skill installed
I need a migration plan to move a Node.js Express API from v14 to v20, switching from CommonJS to ESM and moving from a local MongoDB instance to MongoDB Atlas. I've attached my package.json.
- Read your context and instructions
- Compiled the codebase migration planner
- Generated the document
The migration plan for the Express API focuses on the transition to ESM modules and the shift to managed database infrastructure.
Node.js ESM and MongoDB Atlas Migration Plan
1. Impact Map
| Component | Current | Target | Impact | Risk |
|---|---|---|---|---|
| Runtime | Node.js v14 | Node.js v20 | High (V8 engine changes) | Medium |
| Module System | CommonJS (require) | ESM (import/export) | Critical (Syntax rewrite) | High |
| Database | Local MongoDB | MongoDB Atlas | Network/Auth changes | Low |
| Drivers | mongodb ^3.6.0 | mongodb ^6.0.0 | Breaking API changes | Medium |
2. Phased Execution
Phase 1: Infrastructure & Data
- Task: Provision MongoDB Atlas cluster and configure VPC peering or IP allowlists.
- Verification: Successful connection test using
mongoshfrom the current production environment. - Rollback: Continue pointing to local MongoDB instance.
Phase 2: Dependency & Module Prep
Task: Update package.json with "type": "module" and replace __dirname/__filename references with import.meta.url utilities.
- Task: Upgrade
mongodbdriver to v6.x and refactor connection logic for new Proimse-based APIs. - Verification:
npm testpasses with experimental ESM loader.
Phase 3: Incremental Deployment
- Task: Deploy to staging with Atlas connection string via environment variables.
- Task: Execute dual-run validation to ensure data consistency between local and Atlas instances.
3. Breaking Changes Analysis
Confirmed: require() is not defined in ESM; all internal imports must include file extensions (e.g., ./routes/user.js).
- Likely: Global variables in Node 14 may behave differently in Node 20's stricter environment.
- Needs Verification: Middleware compatibility for older Express plugins under ESM.
Next steps
- Run
grep -r "require(" .to audit all internal dependency imports. - Initialize the Atlas cluster and capture the SRV connection string.
- Update the CI pipeline to test against a Node.js 20 container image.
codebase-migration-planner-pro.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Software migrations are high-risk operations often derailed by hidden dependencies, unverified breaking changes, and lack of rollback procedures. Planning manually leads to architectural drift, data loss, or extended downtime when "quick updates" turn into multi-week debugging sessions.
What it does
- Generates structured impact maps comparing current and target technology stacks.
- Identifies critical path dependencies to determine precise migration sequencing.
- Analyzes source code and manifests to flag specific breaking changes and API risks.
- Produces phased execution plans with validation criteria and rollback triggers for every stage.
- Builds technical runbooks for deployment, including canary rollouts and monitoring requirements.
Why this beats prompting it yourself
Generic prompts often suggest "updating dependencies" without considering transitive risks or stateful data transitions. This skill enforces a strict discovery-first methodology that separates facts from assumptions and mandates validation criteria for every architectural change.
Use cases
- Modernizing legacy monolithic applications into microservices or serverless architectures.
- Upgrading core frameworks, such as migrating from Vue 2 to Vue 3 or React Class components to Hooks.
- Transitioning on-premise infrastructure to cloud-native platforms like AWS or Kubernetes.
- Executing database schema refactors using expand-and-contract patterns to ensure zero downtime.
Known limitations
Cannot execute code or perform actual deployments. Requires user-supplied codebase context or manifests to generate project-specific task IDs and file-level recommendations.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean today
- Passed all security checks, Safe to install