migrate

Generate and apply versioned SQL migrations from Prisma schema changes.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/theslashdojo/dojo --skill migrate-theslashdojo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/theslashdojo/dojo/tree/main/nodes/prisma/migrate
Command: npx skills add https://github.com/theslashdojo/dojo --skill migrate-theslashdojo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires prisma, and includes scripts (resource) components.

What problem does it solve?

Prisma Migrate translates changes in your Prisma schema into versioned SQL migration files and applies them to your database, enabling reliable progression from development to production with traceable migrations.

Core Features & Use Cases

  • Generate versioned SQL migrations from prisma/schema.prisma changes and apply them to your database.
  • Reproduce, test, and recover migrations in dev, staging, and production with status checks and resolution commands.
  • Maintain a clear migration history under prisma/migrations with a timestamped folder per change.

Quick Start

Run a descriptive migration name with Prisma migrate dev to generate and apply a new migration.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I automate Prisma database migrations from schema changes?

You can automate Prisma database migrations by running a descriptive migration name with Prisma migrate dev to generate and apply new versioned SQL migration files directly from your schema.prisma changes.

Can I reproduce and test Prisma migrations across dev and production environments?

Yes, you can reproduce, test, and recover Prisma migrations in dev, staging, and production environments using built-in status checks and resolution commands to ensure reliable progression.

What is the best way to maintain a versioned SQL migration history with Prisma?

The best way to maintain versioned SQL migration history is using Prisma Migrate, which creates a timestamped folder under prisma/migrations for every schema change to ensure traceable database progression.

Does Prisma migrate dev enforce explicit migration creation before deployment?

Yes, the workflow enforces explicit migration creation during development and deployment-only execution in production, ensuring database schema changes are always tracked and applied safely through CLI commands.

How do I recover a failed database schema migration in production?

You can recover a failed database schema migration in production by using the provided resolution commands and recovery safeguards, which allow you to check migration status and rollback or resolve deployment issues.