skills.rest
BryanPinheiro77
BryanPinheiro77COMMUNITY
Explore all skills by this author →
GitHub

migration-architect

Generates phased migration plans, schema compatibility reports, and rollback runbooks from JSON specifications.

2|Updated Mar 24, 2026
Search Tags:#ci/cd#rollback#database#migration#zero-downtime#strangler fig#schema compatibility
One-click install
npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill migration-architect-bryanpinheiro77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration-architect
Source: https://github.com/BryanPinheiro77/FinanceBot-BackEnd/tree/main/.agents/skills/migration-architect
Command: npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill migration-architect-bryanpinheiro77

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Planning database, service, or infrastructure migrations without a structured process leads to unexpected breaking changes, missing rollback paths, and unplanned downtime. This Skill turns a JSON migration specification into a phased plan with risk assessment, validates schema or API compatibility between versions, and produces a rollback runbook for every phase. ## Core Features & Use Cases - Migration Plan Generation: Produces phased plans with validation gates, risk assessment, timeline estimates, and rollback triggers from a migration specification. - Compatibility Checking: Detects breaking and potentially breaking changes between before/after database schemas or API definitions, with suggested migration SQL scripts and exit codes suitable for CI gates. - Rollback Runbook Generation: Creates phase-by-phase rollback procedures, data recovery steps, and communication templates from an existing migration plan. - Use Case: Before altering a production PostgreSQL schema, run the compatibility checker on the old and new schema JSON files; if it exits non-zero, review each breaking change, then generate the migration plan and rollback runbook before approving the cutover. ## Quick Start Ask the assistant to generate a migration plan from your migration specification JSON, then check compatibility between your before and after schema files and produce a rollback runbook for the plan.

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 and potentially breaking changes, suggests migration SQL scripts, and exits 0 only when the schemas are fully compatible.

How do I generate a rollback plan for a database migration?▼

Run rollback_generator.py with the migration plan JSON produced by migration_planner.py as input. It outputs a runbook with phase-by-phase rollback steps, trigger conditions, data recovery procedures, and communication templates.

What input format does the migration planner require?▼

The planner accepts a JSON specification with type (database, service, or infrastructure), pattern (such as schema_change, strangler_fig, or blue_green), source and target descriptions, and constraints like max downtime, data volume, dependencies, and compliance requirements.

Can schema compatibility checks run in a CI/CD pipeline?▼

Yes. compatibility_checker.py returns exit code 0 for compatible schemas, 1 for potentially breaking changes, and 2 for breaking changes, so it can act as a blocking gate in GitHub Actions or similar pipelines.

What counts as a breaking schema change?▼

Breaking changes include removed tables or columns, incompatible type conversions, columns changed from nullable to NOT NULL, required columns added without defaults, and primary key modifications. Each is reported with impact and a suggested migration.

When should I not rely on automated migration planning?▼

Automated plans still require staging-environment validation, load testing, and owner sign-off on every breaking change. The skill treats a migration as unapproved until compatibility checks pass and a tested rollback runbook exists for every phase.

Related Skills

Explore More Software Engineering Skills→
anthrilanthril
3

knowledge-graph-builder

Convert domain concepts into JSON-LD knowledge graph specifications.

Official
Advanced
amanpraajamanpraaj
1

salesforce-data-migration-orchestrator

Plan and execute Salesforce data migrations with staged loads, reconciliation, and cutover controls.

Community
Intermediate
LuigiAPCPereiraLuigiAPCPereira

golang-observability

Implement structured logging, Prometheus metrics, OpenTelemetry tracing, and Grafana dashboards for Go services.

Community
Advanced
inbharataiinbharatai
22

migration-generator

Generate up/down database migration scripts for Alembic, Flyway, and Liquibase.

Community
Intermediate