database-migrations

Enforce safe, reversible database migrations across PostgreSQL, MySQL, and ORMs.

4|Updated Sep 14, 2025
One-click install
npx skills add https://github.com/EvilBit-Labs/DaemonEye --skill database-migrations-evilbit-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-migrations
Source: https://github.com/EvilBit-Labs/DaemonEye/tree/main/.claude/skills/database-migrations
Command: npx skills add https://github.com/EvilBit-Labs/DaemonEye --skill database-migrations-evilbit-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Safe, reversible, and zero-downtime database migrations across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

Core Features & Use Cases

  • Migration safety: enforce UP/DOWN patterns, separate schema and data changes, and provide rollback strategies.
  • Zero-downtime patterns: outline expand-contract, concurrent index creation, and backfill workflows to minimize production impact.
  • Tooling guidance: practical workflows for Prisma, Django, Drizzle, Kysely, and other ecosystems with example migration sequences.

Quick Start

Guide me through implementing safe, zero-downtime migrations for a production database.

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 patterns, concurrent index creation, and explicit backfill workflows to apply schema changes without blocking production traffic.

What is the best way to structure reversible schema changes with ORMs?▼

Reversible schema changes require enforcing strict UP/DOWN migration patterns, separating schema modifications from data updates, and defining clear rollback strategies to ensure safe database migrations.

Does this database migration approach work with Prisma, Django, and Drizzle?▼

Yes, zero-downtime migration guidance covers PostgreSQL and MySQL workflows tailored for popular ORMs including Prisma, Django, Drizzle, Kysely, TypeORM, and golang-migrate.

How do I safely backfill data without locking production database tables?▼

Safe data backfill procedures involve incremental batch updates and concurrent index creation to minimize locking and prevent downtime during large production database migrations.

Why do I need to separate schema changes from data migrations?▼

Separating schema changes from data migrations prevents locking conflicts and allows expand-contract workflows to apply database updates incrementally, ensuring zero-downtime production deployments.

What are the limitations of non-blocking index creation for PostgreSQL and MySQL?▼

Non-blocking index creation minimizes table locks but requires careful execution planning, as concurrent index builds still consume disk space and CPU resources during zero-downtime database migrations.