mcpbeat Sign in

Prisma CLI Migrate Status Skill for Cursor

prisma migrate status

440 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
8
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-status

What comes with it

105 bytes besides the instruction
metadata.json

The instruction itself

8 sections, as written by the author

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_migrations table
  • 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 dev complaining 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.

How to use it

Copy the folder

Take prisma/prisma-cli-migrate-status from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.