migrate

Solid

Migration workflow - research → analyze → plan → implement → review

AI & Automation 552 stars 45 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
91
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /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....

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
8 months ago
Last Updated
6 days ago
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category