prisma-cli

Run prisma migrate dev --name your_migration_name to generate 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.

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, making it the right choice for team development and production-bound changes.

Use prisma migrate deploy, which applies pending migrations without prompts or a shadow database, making it safe for CI/CD pipelines. Run prisma migrate status first to verify the database state before deploying.

Prisma detects AI agent environments and blocks destructive commands like migrate reset and db push --force-reset until the user gives explicit consent. The agent must explain the data-loss impact and pass the exact consent text via PRISMA_USER_CONSENT_FOR_DANGEROUS_AI_ACTION.

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 the CLI shebang.

Avoid db push in production, in team environments needing trackable changes, and whenever you need rollback capability. Use migrate dev and migrate deploy instead, since db push creates no migration history.