database-migrations

Automate safe database migrations across PostgreSQL, MySQL, and common ORMs.

1|Updated Feb 13, 2026

Search Tags:#rollback #database #postgresql #migrations #orm #mysql #zero-downtime

Ready to run

npx skills add https://github.com/ROLLED740/vibe-clone-pro --skill database-migrations-rolled740

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-migrations
Source: https://github.com/ROLLED740/vibe-clone-pro/tree/main/.agent/skills/database-migrations
Command: npx skills add https://github.com/ROLLED740/vibe-clone-pro --skill database-migrations-rolled740

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database migrations are fragile and risky when deployed to production. This guide helps teams plan, test, and rollback schema changes, data migrations, and zero-downtime deployments across PostgreSQL, MySQL, and popular ORMs.

Core Features & Use Cases

Comprehensive migration safety checklist covering UP/DOWN availability, concurrent index creation, and rollback plans.
PostgreSQL, MySQL, and ORM-agnostic patterns for zero-downtime deployments, including expand-contract workflows.
Step-by-step guidance for Prisma, Drizzle, Django, TypeORM, and golang-migrate with concrete examples.

Quick Start

Create a small reversible migration in a staging database and validate UP and DOWN paths with your migration tool.

Frequently Asked Questions about database-migrations

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

FAQPage Schema

How do I perform zero-downtime database migrations in production?▼

Zero-downtime database migrations use expand-contract workflows to separate schema and data changes, ensuring continuous availability. This approach applies standardized safety checklists and ORM-agnostic patterns across PostgreSQL and MySQL to prevent deployment disruptions.

Does this database migration guidance work with Prisma and Drizzle?▼

Yes, the database migration guidance works with Prisma and Drizzle, providing step-by-step examples. It also supports Django, TypeORM, and golang-migrate, offering concrete implementation patterns for schema changes and data migrations across these common ORMs.

What is the best way to plan a database rollback for schema changes?▼

The best way to plan a database rollback is to validate both UP and DOWN migration paths in a staging environment first. This guide provides a comprehensive safety checklist to standardize rollback plans for schema changes and data migrations across PostgreSQL and MySQL.

Why do I need to separate schema and data migrations?▼

Separating schema and data migrations is required to maintain zero-downtime during production deployments. This separation allows database changes to be applied safely without locking tables, enabling expand-contract workflows that satisfy strict availability and rollback safety checklists.

Can I use this for concurrent index creation in PostgreSQL and MySQL?▼

Yes, you can use this for concurrent index creation in PostgreSQL and MySQL. The migration safety checklist explicitly covers concurrent index creation to prevent locking issues, ensuring schema changes do not block production database availability.

How do I test database migrations before deploying to production?▼

To test database migrations before production, create a small reversible migration in a staging database and validate both the UP and DOWN paths. This ensures your rollback plans function correctly and the schema changes satisfy the required safety checklist.