database-migrations

Guide safe database schema changes and data migrations across PostgreSQL, Prisma, Drizzle, Django, and golang-migrate.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Miles0sage/claude-ultimate-stack --skill database-migrations-miles0sage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-migrations
Source: https://github.com/Miles0sage/claude-ultimate-stack/tree/main/skills/database-migrations
Command: npx skills add https://github.com/Miles0sage/claude-ultimate-stack --skill database-migrations-miles0sage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides best practices and patterns for managing database schema changes and data migrations safely and efficiently, preventing data loss and minimizing downtime.

Core Features & Use Cases

  • Schema Evolution: Safely add, alter, or remove tables and columns.
  • Data Migration: Handle complex data transformations and backfills.
  • Zero-Downtime Deployments: Implement strategies for seamless production updates.
  • Tooling Integration: Covers popular tools like Prisma, Drizzle, Django, and golang-migrate.
  • Use Case: You need to add a new is_active boolean column to your users table in PostgreSQL. This Skill guides you through adding it as nullable first, backfilling data, and then making it non-nullable without locking the table.

Quick Start

Use the database-migrations skill to learn how to safely add a new column to a PostgreSQL table using Prisma.

Frequently Asked Questions about database-migrations

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

FAQPage Schema
How do I safely add a non-nullable column to a PostgreSQL table without locking it?

To safely add a non-nullable column in PostgreSQL, add it as nullable first, backfill the existing data, and then enforce the non-nullable constraint to avoid locking the table during schema changes.

What is the best way to manage database schema changes for zero-downtime deployments?

Zero-downtime database schema changes require applying reversible patterns and checklists, ensuring data migrations and backfills occur seamlessly without interrupting production traffic.

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

Yes, this guidance covers specific database migration patterns and tooling integration for both Prisma and Drizzle, alongside Django, PostgreSQL, and golang-migrate.

How do I handle complex data transformations and backfills during schema evolution?

Handle complex data transformations by following established migration patterns that safely separate schema alterations from data backfills, preventing data loss during table alterations.

What are common anti-patterns when running data migrations?

Common database migration anti-patterns include applying non-reversible schema changes and performing massive synchronous backfills that lock tables and cause downtime.