migration

Plan and apply safe database migrations with rollback strategies.

2|Updated Jan 16, 2026

Search Tags:#rollback #database #schema #migration #best-practices #risk-management

Ready to run

npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill migration-mysmon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: migration
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/workflows/migration
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill migration-mysmon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safely planning and applying database migrations is hard: it risks downtime, data loss, and brittle rollouts without clear rollback strategies.

Core Features & Use Cases

Discovery-driven tool identification: Detects the migration configuration and tooling used in a project.
Safe migration patterns: Provides stepwise add/modify/remove column patterns, non-breaking changes, and rollback procedures.
Risk assessment & production readiness: Checks backups, testing in non-production, and drift checks; supports auditable migrations.
Use Case: Teams migrating schemas across PostgreSQL, MySQL, or SQLite using different ORMs can follow a unified safe plan.

Quick Start

Describe your project and I will generate a rollback-ready migration plan.

Frequently Asked Questions about migration

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

FAQPage Schema

How do I plan a database schema migration to prevent data loss and minimize downtime?▼

To perform a safe database schema migration, apply stepwise add/modify/remove column patterns, enforce up/down rollback capabilities, and test changes in non-production environments to prevent data loss and minimize downtime.

What is the best way to handle database schema drift and versioning conflicts during deployments?▼

Handling database schema drift and versioning conflicts requires performing drift checks before production releases. You can resolve discrepancies by applying auditable migration plans that track schema states and ensure versioning consistency across deployments.

Can I use a unified safe migration plan across different ORMs and databases like PostgreSQL, MySQL, and SQLite?▼

Yes, you can apply unified safe migration patterns across PostgreSQL, MySQL, and SQLite regardless of your ORM. The process uses discovery-driven tool identification to detect your project configuration and generates a rollback-ready plan.

How do I generate a rollback strategy for a production database migration?▼

Generating a rollback strategy for a production database migration involves defining up/down migration capabilities and recovery procedures. You must verify backups and run drift checks to ensure the rollback path is safe and auditable.

When should I not use non-breaking schema changes for database migrations?▼

You should reconsider non-breaking schema changes when your database migration involves complex data transformations that cannot be applied stepwise. In these cases, direct structural modifications risk downtime and require rigorous testing in non-production environments first.