database-migrations

Guide safe, reversible database migrations across PostgreSQL, MySQL, and common ORMs.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ValenBorras/upscribe --skill database-migrations-valenborras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-migrations
Source: https://github.com/ValenBorras/upscribe/tree/main/.github/skills/database-migrations
Command: npx skills add https://github.com/ValenBorras/upscribe --skill database-migrations-valenborras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database migrations can be risky and hard to audit; this Skill provides best practices for safely applying schema changes, data migrations, and rollbacks across PostgreSQL, MySQL, and common ORMs.

Core Features & Use Cases

  • Clear framework for applying, testing, and auditing migrations across multiple environments.
  • Covers schema changes, data migrations (backfills), rollback strategies, and zero-downtime deployment patterns.
  • Suitable for Prisma, Drizzle, Django, TypeORM, and other ORMs to enforce consistent migration workflows.

Quick Start

Define a migration plan that separates schema and data changes, validate against staging data, and document rollback steps.

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 require separating schema changes from data backfills to avoid locking tables. This framework enforces validation checks and reversible UP/DOWN scripts to ensure non-breaking deployments in production.

Can I use this database migration workflow with Prisma and TypeORM?

Yes, this migration workflow supports common ORMs including Prisma, TypeORM, Drizzle, and Django. It enforces consistent migration artifacts and rollback strategies across PostgreSQL and MySQL environments.

What is the best way to structure a rollback for a failed schema change?

The best way to structure a rollback is by maintaining explicit DOWN scripts paired with UP scripts. This framework guides teams in documenting and safely executing reversible schema changes and data migrations.

Why should I separate schema changes from data backfills during a migration?

Separating schema changes from data backfills prevents table locks and ensures zero-downtime deployment. This framework enforces this separation to validate non-breaking migrations across staging and production environments.

How do I test database migrations before applying them to production?

You test migrations by defining a plan that separates schema and data changes, then validating it against staging data. This process ensures rollback steps are documented and deployment checks pass before production rollout.