database-migrations

Plan and execute database migrations across Supabase, Prisma, and Drizzle ORM.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Naw3/skillsrepo --skill database-migrations-naw3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-migrations
Source: https://github.com/Naw3/skillsrepo/tree/main/database-migrations
Command: npx skills add https://github.com/Naw3/skillsrepo --skill database-migrations-naw3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured guidance for migrating database schemas across popular ORMs (Supabase, Prisma, and Drizzle), helping teams avoid downtime, data loss, and risky migrations.

Core Features & Use Cases

  • Migration patterns: Non-blocking column additions, safe renames, and zero-downtime index changes across PostgreSQL-backed schemas.
  • Cross-ORM scaffolding: Examples and best practices for Supabase migrations, Prisma migrations, and Drizzle migrations in a unified workflow.
  • Use Case: When evolving a production schema, use this skill to plan, implement, test, and rollback migrations with confidence, covering development, staging, and production.

Quick Start

Plan a migration by selecting a safe pattern; document steps, tests, and rollback.

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 with Prisma and PostgreSQL?

Zero-downtime database migrations require non-blocking schema changes like delayed column drops and concurrent index builds. This skill guides safe Prisma migration patterns across PostgreSQL-backed stacks, ensuring rollout readiness without locking tables.

What is the best way to manage schema evolution across Supabase and Drizzle?

Cross-ORM schema evolution involves unified migration scaffolding and consistent rollout planning. This skill provides structured best practices and concrete examples for managing Supabase migrations and Drizzle migrations safely.

How do I plan a rollback for a production database migration?

Production database migration rollback planning requires documenting every schema change step and preparing reverse operations. This skill enforces rollback readiness by integrating concrete checklists into your development, staging, and production workflow.

Does this database migration approach work for both Supabase and Prisma?

Yes, this database migration approach works for both Supabase and Prisma, alongside Drizzle. It provides enterprise-grade guidance for production deployments, ensuring cross-ORM consistency and safe schema evolution across PostgreSQL-backed stacks.

Why do PostgreSQL database migrations cause downtime and how can I avoid it?

PostgreSQL database migrations cause downtime when schema changes lock tables or block concurrent operations. You can avoid it by applying non-blocking migration patterns like safe renames and zero-downtime index changes provided by this skill.

When do I need to use non-blocking migration patterns for schema changes?

Non-blocking migration patterns are needed when evolving a production schema where downtime or data loss is unacceptable. This skill helps you plan, test, and implement safe database migrations with confidence across your PostgreSQL stack.