migration-architect

Generates migration plans, compatibility reports, and rollback runbooks for database and service migrations.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill migration-architect-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-architect
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/migration-architect
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill migration-architect-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Planning a database, service, or infrastructure migration without a structured process leads to unexpected breaking changes, missing rollback paths, and unplanned downtime. This Skill turns a migration spec into a phased plan, validates schema and API compatibility as a CI gate, and produces a rollback runbook for every phase. ## Core Features & Use Cases - Migration Plan Generation: Convert a migration spec JSON into a phased plan with risks and estimated duration using migration_planner.py. - Compatibility Checking: Detect breaking and potentially breaking schema or API changes (type changes, removed columns, new required fields) with compatibility_checker.py, exiting non-zero unless fully compatible. - Rollback Runbook Generation: Produce rollback procedures for every migration phase with rollback_generator.py. - Use Case: Before migrating a production PostgreSQL schema, run the compatibility checker on the before/after schema JSON files in CI, block the deploy on any breaking change, and attach the generated rollback runbook to the change request. ## Quick Start Plan a database migration by generating a migration plan from my spec, checking schema compatibility between the old and new versions, and creating a rollback runbook for each phase.

Frequently Asked Questions about migration-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check database schema compatibility before a migration?▼

Run compatibility_checker.py with --before and --after schema JSON files and --type database. It reports breaking changes like removed columns, incompatible type changes, and new NOT NULL constraints, exiting non-zero unless the schema is fully compatible.

How to generate a rollback plan for a database migration?▼

Pipe the output of migration_planner.py into rollback_generator.py with --format both to produce a rollback runbook covering every migration phase. The skill requires a rollback runbook per phase before a migration is approved.

What is the expand-contract pattern for schema migrations?▼

Expand-contract adds new columns or tables alongside the old schema, dual-writes during a transition period, backfills data, then removes the old schema after validation. It enables zero-downtime schema changes with a safe rollback point at each stage.

Can compatibility checking run in a CI/CD pipeline?▼

Yes, compatibility_checker.py exits non-zero unless overall_compatibility is compatible, making it usable as a CI gate. The skill documents a pipeline stage that runs the checker and planner and archives the JSON reports as artifacts.

What types of changes does the compatibility checker detect?▼

It detects removed tables and columns, incompatible data type changes, nullability restrictions, length reductions, added or removed constraints, removed API endpoints, changed required parameters, and response schema changes, each classified as breaking, potentially breaking, or non-breaking.

When should I use the strangler fig pattern instead of a big bang migration?▼

Use strangler fig when replacing a legacy service incrementally: route traffic through a gateway, shift functionality to the new service piece by piece, and retire legacy components as the new ones prove stable. Big bang migrations are an anti-pattern due to high failure risk and difficult rollback.