
prisma-cli-migrate-status
✓ Official★ 8by prisma · part of prisma/cursor-plugin
prisma migrate status
prisma migrate status
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
by prisma
prisma migrate status
npx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-status
Download ZIPGitHub8
prisma migrate status
Checks the status of your database migrations.
Command
prisma migrate status [options]
What It Does
-
Connects to the database
-
Checks the
_prisma_migrationstable -
Compares applied migrations with local migration files
-
Reports:
-
Status: Database is up-to-date or behind
-
Unapplied migrations: Count of pending migrations
-
Missing migrations: Migrations present in DB but missing locally
-
Failed migrations: Any migrations that failed to apply
Options
Option Description
--schema Path to schema file
--config Custom path to your Prisma config file
Examples
Check status
prisma migrate status
Output example (Up to date):
Database schema is up to date!
Output example (Pending):
Following migration have not yet been applied:
20240115120000_add_user
To apply migrations in development, run:
prisma migrate dev
To apply migrations in production, run:
prisma migrate deploy
When to Use
-
Debugging: Why is
migrate devcomplaining about drift? -
CI/CD: Verify database state before deploying
-
Production: Check if migrations are needed (
migrate deploy) or if a deployment failed
Exit Codes
-
0: Success (may have pending migrations, but command ran successfully) -
1: Error
To check for pending migrations programmatically, you might need to parse the output or use migrate diff with exit code flags.
npx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-statusRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.