
migrate
Migration workflow - research → analyze → plan → implement → review
- Installs
- 481
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill migrate- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads migrate automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/migrate - Migration Workflow
Safe migrations for frameworks, languages, and infrastructure.
When to Use
- "Migrate to X"
- "Upgrade framework"
- "Move from X to Y"
- "Upgrade Python/Node/etc."
- "Migrate database"
- Framework version upgrades
- Language migrations
- Infrastructure changes
Workflow Overview
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐ ┌───────────┐
│ oracle │───▶│ phoenix │───▶│ plan- │───▶│ kraken │───▶│ surveyor │
│ │ │ │ │ agent │ │ │ │ │
└──────────┘ └──────────┘ └────────────┘ └──────────┘ └───────────┘
Research Analyze Plan Implement Review
target current migration changes migration
Agent Sequence
| # | Agent | Role | Output |
|---|---|---|---|
| 1 | oracle | Research target framework/version | Research report |
| 2 | phoenix | Analyze current codebase for migration impact | Impact analysis |
| 3 | plan-agent | Create phased migration plan | Migration plan |
| 4 | kraken | Implement migration changes | Code changes |
| 5 | surveyor | Review migration for completeness | Migration review |
Why Extra Gates?
Migrations are high-risk:
- Breaking changes between versions
- Dependency conflicts
- Data format changes
- API deprecations
The extra research and review phases catch issues early.
Execution
Phase 1: Research Target
Task(
subagent_type="oracle",
prompt="""
Research migration target: [TARGET]
Investigate:
- Breaking changes from current version
- New APIs and patterns
- Deprecated features we use
- Migration guides from official docs
- Common pitfalls and solutions
Output: Migration research report
"""
)
Phase 2: Analyze Current State
Task(
subagent_type="phoenix",
prompt="""
Analyze codebase for migration: [FROM] → [TO]
Identify:
- Files using deprecated APIs
- Dependency conflicts
- Patterns that need updating
- Test coverage of affected areas
- Risk areas (critical paths)
Output: Impact analysis with affected files
"""
)
Phase 3: Plan Migration
Task(
subagent_type="plan-agent",
prompt="""
Create migration plan: [FROM] → [TO]
Research: [from oracle]
Impact: [from phoenix]
Plan should:
- Be phased (incremental if possible)
- Each phase independently testable
- Include rollback strategy
- Prioritize critical path stability
Output: Phased migration plan
"""
)
Phase 4: Implement
Task(
subagent_type="kraken",
prompt="""
Implement migration phase: [PHASE_N]
Plan: [from plan-agent]
Requirements:
- Follow plan exactly
- Run tests after each change
- Document any deviations
- Stop if tests fail
Output: Completed phase with test results
"""
)
Phase 5: Review Migration
Task(
subagent_type="surveyor",
prompt="""
Review migration: [FROM] → [TO]
Check:
- All deprecated APIs replaced
- No remaining compatibility shims
- Tests passing
- Performance acceptable
- No security regressions
Output: Migration review report
"""
)
Migration Types
Framework Upgrade
User: /migrate React 17 → 18
→ Full workflow with hooks/concurrent mode changes
Language Version
User: /migrate Python 3.9 → 3.12
→ Focus on new syntax, removed features
Database Migration
User: /migrate MongoDB → PostgreSQL
→ Schema design, data transformation, query rewrite
Infrastructure
User: /migrate AWS → GCP
→ Service mapping, config translation
Example
User: /migrate from Express to Fastify
Claude: Starting /migrate workflow: Express → Fastify
Phase 1: Researching Fastify...
[Spawns oracle]
Key differences:
- Schema-based validation (vs middleware)
- Plugin architecture
- Async/await native
- Different middleware pattern
Phase 2: Analyzing current Express usage...
[Spawns phoenix]
Impact analysis:
- 23 route files to update
- 8 middleware to convert
- 3 plugins need Fastify equivalents
- Test coverage: 78%
Phase 3: Creating migration plan...
[Spawns plan-agent]
Migration Plan: Express → Fastify
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Phase 1: Setup & Core
- Add Fastify alongside Express
- Migrate core server setup
- Run both in parallel
Phase 2: Routes (by domain)
- Migrate auth routes
- Migrate user routes
- Migrate product routes
- ...
Phase 3: Middleware
- Convert error handler
- Convert auth middleware
- Convert logging
Phase 4: Cleanup
- Remove Express
- Remove compatibility layer
- Final testing
Rollback: Keep Express until Phase 4 complete
Phase 4: Implementing Phase 1...
[Spawns kraken]
✅ Fastify server running alongside Express
✅ Core routes migrated
✅ Tests passing
[Continues through phases...]
Phase 5: Reviewing migration...
[Spawns surveyor]
✅ All Express code removed
✅ 23/23 routes migrated
✅ Performance improved (2.1x faster)
✅ No security regressions
Migration complete! Express → Fastify
Incremental Migration
For large codebases, run one phase at a time:
User: /migrate React 17 → 18 --phase 1
[Runs only Phase 1]
User: /migrate React 17 → 18 --phase 2
[Runs Phase 2, reads previous handoff]
Flags
--phase N: Run specific phase only--dry-run: Plan without implementing--rollback: Execute rollback plan--parallel: Run new alongside old (strangler fig)
FAQ
What does the migrate skill do?
Migration workflow - research → analyze → plan → implement → review
How do I install migrate?
Run npx skills add https://github.com/parcadei/continuous-claude-v3 --skill migrate in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/migrate/ (personal) or .claude/skills/migrate/ (project).
Which AI agents can use migrate?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is migrate safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains migrate?
It is published by parcadei in parcadei/continuous-claude-v3. It has 481 recorded installs.
More from parcadei/continuous-claude-v3
discovery-interview
parcadei/continuous-claude-v3
Deep interview process to transform vague ideas into detailed specs. Works for technical and non-technical users.
premortem
parcadei/continuous-claude-v3
Identify failure modes before they occur using structured risk analysis
math
parcadei/continuous-claude-v3
Unified math capabilities - computation, solving, and explanation. I route to the right tool.
github-search
parcadei/continuous-claude-v3
Search GitHub code, repositories, issues, and PRs via MCP
dead-code
parcadei/continuous-claude-v3
Find unused functions and dead code in the codebase
refactor
parcadei/continuous-claude-v3
Code refactoring workflow - analyze → plan → implement → review → validate
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.