@sshaaf/migiq
v0.2.2
Published
AI-powered application migration orchestrator for modernizing legacy applications to cloud-native platforms
Downloads
451
Maintainers
sshaafReadme
MigIQ - Intelligent Application Migration Platform
AI-powered application migration orchestrator for modernizing legacy applications to cloud-native platforms.
🚀 Quick Start
Install MigIQ for Claude Code with a single command:
# Install to local project .claude directory (recommended)
npx @sshaaf/migiq
# Or install globally to ~/.claude
npx @sshaaf/migiq -gThen in Claude Code:
/migiq
"Migrate this Spring Boot app to Quarkus"Or for autonomous migration:
Agent({
description: "Spring Boot to Quarkus migration",
prompt: "Follow AGENT.md. Migrate this Spring Boot application to Quarkus...",
subagent_type: "general-purpose"
})Overview
MigIQ is a comprehensive migration solution that combines knowledge graph analysis, intelligent planning, and autonomous execution to migrate applications across platforms, frameworks, and languages.
Two Execution Modes
Interactive Mode (/migiq skill)
Best for:
- Learning how migrations work
- Migrations < 1 hour
- Active participation desired
- Approving each phase
Usage:
cd my-app
# In Claude Code:
/migiq
"Migrate to [target technology]"Autonomous Mode (Migrator Agent)
Best for:
- Migrations > 1 hour
- Background/overnight work
- Parallel multi-app migrations
- When you trust the process
Usage:
Follow AGENT.md. Migrate from Spring Boot to Quarkus...
🏗️ Architecture
The MigIQ Ecosystem
┌─────────────────────────────────────────────────────────────┐
│ MigIQ Platform │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌──────────────┐ ┌─────────────────────┐ │
│ │ /migiq │ │ Migrator Agent │ │
│ │ Skill │◄────────────►│ (AGENT.md) │ │
│ │ │ │ │ │
│ │ Interactive │ │ Autonomous │ │
│ │ Orchestration│ │ Long-running │ │
│ └──────┬───────┘ └──────────┬──────────┘ │
│ │ │ │
│ └─────────────┬───────────────────┘ │
│ │ │
│ ┌─────────────▼────────────────┐ │
│ │ Core Migration Skills │ │
│ ├──────────────────────────────┤ │
│ │ │ │
│ │ 1. mig-graphify │ ← Analysis │
│ │ 2. mig-prompt-builder │ ← Requirements │
│ │ 3. mig-plan │ ← Planning │
│ │ 4. mig-execute │ ← Execution │
│ │ 5. mig-test-gen │ ← Testing │
│ │ 6. mig-containerize │ ← Containers │
│ │ 7. mig-deploy │ ← Deployment │
│ │ │ │
│ └──────────────────────────────┘ │
│ │
└───────────────────────────────────────────────────────────--┘5-Phase Migration Workflow
Phase 1: Analysis Phase 2: Requirements Phase 3: Planning
┌──────────────-┐ ┌──────────────────┐ ┌─────────────┐
│ mig-graphify │ │ mig-prompt- │ │ mig-plan │
│ │ │ builder │ │ │
│ • Code graph │ ────► │ │ ────► │ • tasks.md │
│ • Dependencies│ │ • Source tech │ │ • stories │
│ • Architecture│ │ • Target tech │ │ │
│ • Complexity │ │ • Constraints │ │ (uses │
└──────────────-┘ │ • migration- │ │ migration- │
│ prompt.md │ │ prompt.md) │
└──────────────────┘ └─────────────┘
│
▼
Phase 5: Reporting Phase 4: Execution
┌──────────────┐ ┌─────────────────────────┐
│ Final Report │ ◄──── │ mig-execute │
│ │ │ │
│ • Summary │ │ • Code changes │
│ • Metrics │ │ • Tests (mig-test-gen) │
│ • Next steps │ │ • Containers │
│ │ │ • OpenShift manifests │
└──────────────┘ └─────────────────────────┘🎯 Many Use Cases (supports 31 languages)
1. Platform Migrations
- Java EE → Spring Boot → Quarkus
- .NET Framework → .NET 8
- Node.js 12 → Node.js 20
- Rails → Node.js/Python
2. Cloud Migrations
- On-prem → OpenShift
- Traditional VMs → Containers
- Monolith → Microservices
3. Modernization
- Legacy patterns → Modern idioms
- Callbacks → async/await
- Old dependencies → Latest versions
- Manual deployment → CI/CD
4. Language Migrations
- Java → Kotlin
- JavaScript → TypeScript
- Python 2 → Python 3
5. Target Platforms
- Quarkus, Spring Boot, Micronaut (Java/JVM)
- Node.js (modern), Next.js, Remix (JavaScript/TypeScript)
- FastAPI, Django 4+ (Python)
- .NET 8 (C#)
6. Deployment Targets
- Red Hat OpenShift (primary)
- Kubernetes
- Container platforms (Docker, Podman)
📊 What You Get
After a migration, you'll have:
your-project/
├── graphify-out/ # Phase 1: Analysis
│ ├── graph.json # Knowledge graph
│ ├── GRAPH_REPORT.md # Analysis report
│ └── graph.html # Interactive visualization
│
├── mig-prompt-workspace/ # Phase 2: Requirements
│ └── migration-prompt.md # Standardized prompt
│
├── mig-plan-workspace/ # Phase 3: Planning
│ ├── tasks.md # Detailed task breakdown
│ └── UserStory.md # User stories
│ # Note: spec/design in migration-prompt.md (Phase 2)
│
├── mig-execute-workspace/ # Phase 4: Execution
│ ├── EXECUTION_REPORT.md # Execution results
│ ├── execution-log.md # Detailed timeline
│ └── outputs/
│ ├── tests/ # Generated tests
│ ├── containers/ # Dockerfiles
│ └── deployments/ # OpenShift YAMLs
│
└── migiq-workspace/ # Phase 5: Orchestration
├── orchestration-log.md # Full orchestration log
└── MIGRATION_REPORT.md # ⭐ Share with stakeholdersthe examples/spring-boot-to-quarkus.tar.gz has an example of a completed migration, deployed to OpenShift.
📚 Documentation
Getting Started
- migiq/README.md - Skill quick start
Deep Dives
- migiq/SKILL.md - Complete orchestration workflow
- AGENT.md - Autonomous agent definition
- migiq/TEST_PLAN.md - Testing strategy
Individual Skills
- mig-graphify/SKILL.md - Code analysis
- mig-prompt-builder/SKILL.md - Requirements
- mig-plan/SKILL.md - Planning
- mig-execute/SKILL.md - Execution
Documentation
Debugging
- Check
orchestration-log.mdfor workflow trace - Review
execution-log.mdfor detailed timeline - Validate outputs with
test-validator.sh
Issues
For bugs or feature requests, document:
- Source and target technologies
- Migration phase that failed
- Error messages from logs
- Steps to reproduce
Ready to migrate? Start with migiq/README.md