doncheli-migrate
A structured planning tool for technology migrations with risk-based task waves.
Install
mkdir -p .claude/skills/doncheli-migrate && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14157" && unzip -o skill.zip -d .claude/skills/doncheli-migrate && rm skill.zipInstalls to .claude/skills/doncheli-migrate
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Plan and execute technology migrations with wave planning, breaking change detection and task generation. Activate when user mentions "migrate", "migration", "upgrade", "move from", "switch to", "Vue to React", "JS to TS", "v1 to v2".Key capabilities
- →Identify source and target technologies for migration
- →Scan codebase to inventory affected modules and dependencies
- →Build an equivalence map between old and new patterns/APIs
- →Detect breaking changes and suggest mitigations
- →Produce a wave plan ordered by risk and dependency graph
How it works
The skill identifies source and target technologies, scans the codebase for affected components, and then generates an equivalence map and detects breaking changes. It then organizes the migration into a phased wave plan with atomic tasks.
Inputs & outputs
When to use doncheli-migrate
- →Migrating from vue to react
- →Upgrading framework versions
- →Switching languages (JS to TS)
- →Planning infrastructure migrations
About this skill
Don Cheli: Migration Planner
Instructions
- Identify source stack/version and target stack/version
- Scan the codebase (or description) to inventory affected modules, dependencies, patterns
- Build the equivalence map:
source construct → target construct - Detect breaking changes (API removals, semantic shifts, config format changes)
- Produce a wave plan ordered by risk and dependency graph (low-risk, foundational first)
- Generate atomic migration tasks, each independently deployable or reviewable
Output Format
## Migration Plan: <source> → <target>
### Equivalence Map
| Source | Target | Notes |
|-------------------------|-------------------------------|----------------|
| <old pattern/API> | <new pattern/API> | … |
### Breaking Changes
1. <change> — Impact: <high/medium/low> — Mitigation: …
…
### Wave Plan
**Wave 1 — Foundation (lowest risk)**
- [ ] Task: …
- [ ] Task: …
**Wave 2 — Core Migration**
- [ ] Task: …
**Wave 3 — Cleanup & Optimization**
- [ ] Task: …
### Rollback Strategy
…
### Definition of Done
- [ ] All tests pass on target stack
- [ ] No references to deprecated source APIs remain
- [ ] Performance benchmarks ≥ baseline
Quality Gate
- Every breaking change must have an explicit mitigation
- Wave 1 must be deployable independently without completing later waves
- If the migration affects >10 files, confirm scope with the user before generating all tasks
Do not use this skill when
- The change is a minor dependency bump with no API changes (use a standard fix commit)
- The user only wants to understand differences, not plan tasks (use doncheli-reasoning instead)
When not to use it
- →When the change is a minor dependency bump with no API changes
- →When the user only wants to understand differences, not plan tasks
Limitations
- →Every breaking change must have an explicit mitigation
- →Wave 1 must be deployable independently without completing later waves
- →If the migration affects >10 files, confirm scope with the user before generating all tasks
How it compares
This skill automates the structured planning of technology migrations, including breaking change detection and task generation, which is more systematic than a manual, ad-hoc approach.
Compared to similar skills
doncheli-migrate side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| doncheli-migrate (this skill) | 0 | 4mo | No flags | Advanced |
| software-architecture | 333 | 6mo | No flags | Intermediate |
| solid-principles | 57 | 9mo | No flags | Intermediate |
| codex | 32 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by doncheli
View all by doncheli →You might also like
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.
game-development
davila7
Game development orchestrator. Routes to platform-specific skills based on project needs.
senior-fullstack
davila7
Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.
oracle
openclaw
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).