prisma-cli

Reference Prisma ORM CLI commands for migrations, client generation, and database workflows.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/soumeningit/FlowBoard --skill prisma-cli-soumeningit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prisma-cli
Source: https://github.com/soumeningit/FlowBoard/tree/main/packages/database/.windsurf/skills/prisma-cli
Command: npx skills add https://github.com/soumeningit/FlowBoard --skill prisma-cli-soumeningit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers working with Prisma ORM need accurate, current guidance on CLI commands for initializing projects, generating clients, running migrations, and managing databases, without confusing the ORM CLI with the separate Prisma Platform CLI. ## Core Features & Use Cases - Command Reference: Covers init, generate, migrate, db push/pull/seed/execute, dev, studio, validate, format, debug, complete, and mcp with options and examples. - Migration Workflows: Distinguishes development workflows (migrate dev) from production deployments (migrate deploy) and recovery tools (migrate resolve, migrate status). - AI Safety Checkpoint: Documents the consent requirement for destructive commands like migrate reset and db push --force-reset when run by AI agents. - Use Case: When setting up a new project, follow the init reference to create prisma.config.ts, start a local database with prisma dev, then run migrate dev and generate to get a working typed client. ## Quick Start Ask the assistant to show how to create and apply a named Prisma migration and then regenerate the Prisma Client.

Frequently Asked Questions about prisma-cli

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

FAQPage Schema
How do I create and apply a Prisma migration in development?▼

Run prisma migrate dev --name your_migration_name to create and apply a migration from schema changes. It uses a shadow database for drift detection, and you should run prisma generate afterward to refresh the client.

What is the difference between prisma db push and prisma migrate dev?▼

db push syncs the schema directly without creating migration files or history, making it suited for prototyping and MongoDB. migrate dev creates tracked migration files with rollback capability, which is better for team development and production paths.

How do I apply Prisma migrations in production?▼

Use prisma migrate deploy in CI/CD or production environments. It applies pending migrations without prompts, drift detection, or a shadow database, and never generates new migrations.

Does Prisma block destructive commands when run by an AI agent?▼

Yes. Prisma blocks migrate reset, db push --force-reset, and db push --accept-data-loss when it detects an AI agent until the user gives explicit consent. The exact consent text can be passed via the PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION environment variable.

Can I use Prisma CLI with Bun instead of Node.js?▼

Yes, but you must add the --bun flag, for example bunx --bun prisma generate. Without it, the CLI falls back to Node.js because of its shebang.

When should I not use prisma db push?▼

Avoid db push in production, in team environments needing trackable changes, and when you need rollback capability. Use migrate dev and migrate deploy instead for those scenarios.