Safe migrations for frameworks, languages, and infrastructure.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmigrateExecute the skills CLI command in your project's root directory to begin installation:
Fetches migrate from parcadei/continuous-claude-v3 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate migrate. Access via /migrate in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
Safe migrations for frameworks, languages, and infrastructure.
┌──────────┐ ┌──────────┐ ┌────────────┐ ┌──────────┐ ┌───────────┐
│ oracle │───▶│ phoenix │───▶│ plan- │───▶│ kraken │───▶│ surveyor │
│ │ │ │ │ agent │ │ │ │ │
└──────────┘ └──────────┘ └────────────┘ └──────────┘ └───────────┘
Research Analyze Plan Implement Review
target current migration changes migration
| # | 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 |
Migrations are high-risk:
The extra research and review phases catch issues early.
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
"""
)
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
"""
)
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
"""
)
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
"""
)
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
"""
)
User: /migrate React 17 → 18
→ Full workflow with hooks/concurrent mode changes
User: /migrate Python 3.9 → 3.12
→ Focus on new syntax, removed features
User: /migrate MongoDB → PostgreSQL
→ Schema design, data transformation, query rewrite
User: /migrate AWS → GCP
→ Service mapping, config translation
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
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]
--phase N: Run specific phase only--dry-run: Plan without implementing--rollback: Execute rollback plan--parallel: Run new alongside old (strangler fig)Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for migrate matched our evaluation — installs cleanly and behaves as described in the markdown.
migrate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added migrate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
migrate reduced setup friction for our internal harness; good balance of opinion and flexibility.
migrate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for migrate matched our evaluation — installs cleanly and behaves as described in the markdown.
migrate reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for migrate matched our evaluation — installs cleanly and behaves as described in the markdown.
We added migrate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
migrate is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 34