Prisma Cli Migrate Resolve

Name: Prisma Cli Migrate Resolve
Author: prisma

prisma/cursor-plugin

12 installs
8 repo stars
Updated February 9, 2026
prisma/cursor-plugin

prisma-cli-migrate-resolve fixes Prisma migration table state after failures.

About

The prisma-cli-migrate-resolve skill documents Prisma migrate resolve for manual _prisma_migrations state fixes. Exactly one of --applied or --rolled-back must be provided with the migration name. Marking applied baselines existing databases without re-running SQL during adoption on production schemas. Marking rolled back recovers from failed migrate deploy runs so SQL can be fixed and reapplied. Options include --schema and --config for custom paths. Use cases cover baselining brownfield databases, recovering failed production deploys, and rare hotfix reconciliation. References link to Prisma baselining and production troubleshooting guides.

Updates _prisma_migrations via applied or rolled-back flags.
Baselines existing databases without executing SQL.
Recovers failed migrate deploy after SQL fixes.
Requires exactly one of --applied or --rolled-back.
Supports custom schema and config paths.

Prisma Cli Migrate Resolve by the numbers

12 all-time installs (skills.sh)
Ranked #636 of 911 Databases skills by installs in the Skillselion catalog
Data as of Aug 4, 2026 (Skillselion catalog sync)

At a glance

prisma-cli-migrate-resolve capabilities & compatibility

Capabilities: applied baselining workflow · rolled back failure recovery · use cases baselining and hotfixes
Works with: postgres · mysql · mongodb
Use cases: database · devops

npx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-resolve

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/prisma/cursor-plugin/prisma-cli-migrate-resolve.svg)](https://skillselion.com/skills/prisma/cursor-plugin/prisma-cli-migrate-resolve)

Installs	12
repo stars	★ 8
Last updated	February 9, 2026
Repository	prisma/cursor-plugin ↗

How do I mark a failed Prisma migration rolled back?

Recover failed Prisma migrations by marking them applied or rolled back.

Who is it for?

Teams adopting or recovering Prisma Migrate on production databases.

Skip if: Skip for greenfield migrate dev flows without history conflicts.

When should I use this skill?

Migration failed, needs baselining, or migrate resolve recovery.

What you get

Updated migration history ready for redeploy or baseline.

Files

SKILL.mdMarkdownGitHub ↗

prisma migrate resolve

Resolves issues with database migrations, such as failed migrations or baselining.

Command

prisma migrate resolve [options]

What It Does

Updates the _prisma_migrations table to manually change the state of a migration. This is a recovery tool.

Options

You must provide exactly one of --applied or --rolled-back.

Option	Description
`--applied <name>`	Mark a migration as applied (success)
`--rolled-back <name>`	Mark a migration as rolled back (ignored/failed)
`--schema`	Path to schema file
`--config`	Custom path to your Prisma config file

Examples

Mark as Applied (Baselining)

If you have existing tables and want to initialize migrations without running the SQL:

prisma migrate resolve --applied 20240101000000_initial_migration

This tells Prisma "Assume this migration has already run".

Mark as Rolled Back (Fixing Failures)

If a migration failed (e.g., syntax error) and you fixed the SQL or want to retry:

prisma migrate resolve --rolled-back 20240115120000_failed_migration

This tells Prisma "Forget this migration run, let me try applying it again".

Use Cases

1. Baselining: Adopting Prisma Migrate on an existing production database. 2. Failed Migrations: Recovering from a failed migrate deploy in production. 3. Hotfixes: reconciling manual database changes (rare).