Install
Quick install
npx skills add https://github.com/prisma/cursor-plugin/tree/HEAD/skills/prisma-cli-migrate-statusnpx skills add prisma/cursor-plugin --skill prisma-cli-migrate-status --agent claude-codenpx skills add prisma/cursor-plugin --skill prisma-cli-migrate-status --agent cursornpx skills add prisma/cursor-plugin --skill prisma-cli-migrate-status --agent codexnpx skills add prisma/cursor-plugin --skill prisma-cli-migrate-status --agent opencodenpx skills add prisma/cursor-plugin --skill prisma-cli-migrate-status --agent github-copilotnpx skills add prisma/cursor-plugin --skill prisma-cli-migrate-status --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add prisma/cursor-plugin --skill prisma-cli-migrate-statusManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/prisma/cursor-plugin.gitcp -r cursor-plugin/skills/prisma-cli-migrate-status ~/.claude/skills/prisma-cli-migrate-status
prisma migrate status
prisma-cli-migrate-statusby prisma
prisma migrate statusnpx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-statusDownload ZIPGitHub
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
OptionDescription--schemaPath to schema file--configCustom 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.
More skills from prisma
prisma-cli-studioby prismaprisma studio. Reference when using this Prisma feature.prisma-cli-validateby prismaprisma validate. Reference when using this Prisma feature.prisma-cli-db-executeby prismaprisma db execute. Reference when using this Prisma feature.prisma-cli-db-pullby prismaprisma-cli-db-pull — an installable skill for AI agents, published by prisma/cursor-plugin.prisma-cli-db-pushby prismaprisma db push. Reference when using this Prisma feature.prisma-cli-db-seedby prismaprisma db seed. Reference when using this Prisma feature.prisma-cli-debugby prismaprisma debug. Reference when using this Prisma feature.prisma-cli-devby prismaprisma dev. Reference when using this Prisma feature.---
Source: https://github.com/prisma/cursor-plugin/tree/HEAD/skills/prisma-cli-migrate-status
Author: prisma
Discovered via: mcpservers.org
SKILL.md source
--- name: prisma-cli-migrate-status description: prisma migrate status --- # prisma-cli-migrate-status prisma migrate status # prisma-cli-migrate-statusby prisma prisma migrate status `npx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-status`Download ZIPGitHub ## 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 OptionDescription`--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. ## More skills from prisma prisma-cli-studioby prismaprisma studio. Reference when using this Prisma feature.prisma-cli-validateby prismaprisma validate. Reference when using this Prisma feature.prisma-cli-db-executeby prismaprisma db execute. Reference when using this Prisma feature.prisma-cli-db-pullby prismaprisma-cli-db-pull — an installable skill for AI agents, published by prisma/cursor-plugin.prisma-cli-db-pushby prismaprisma db push. Reference when using this Prisma feature.prisma-cli-db-seedby prismaprisma db seed. Reference when using this Prisma feature.prisma-cli-debugby prismaprisma debug. Reference when using this Prisma feature.prisma-cli-devby prismaprisma dev. Reference when using this Prisma feature. --- **Source**: https://github.com/prisma/cursor-plugin/tree/HEAD/skills/prisma-cli-migrate-status **Author**: prisma **Discovered via**: mcpservers.org
Related skills 6
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
secure-linux-web-hosting
Use when setting up, hardening, or reviewing a cloud server for self-hosting, including DNS, SSH, firewalls, Nginx, static-site hosting, reverse-proxying an app, HTTPS with Let's Encrypt or ACME clients, safe HTTP-to-HTTPS redirects, or optional post-launch network tuning such as BBR.
readme-i18n
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
lark-shared
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
paper-context-resolver
Optional RigorPilot helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacin...