prisma-cli

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.

db push syncs the schema directly without creating migration files, making it faster for prototyping and required for MongoDB. migrate dev creates tracked migration files with history and rollback capability, suited for team development.

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

Prisma detects AI agent environments and blocks destructive commands like migrate reset until the user gives explicit consent. The agent must explain the data-loss impact and obtain consent immediately before running the command.

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 collaboration requiring trackable changes, and when you need rollback capability. Use migrate dev and migrate deploy instead for those scenarios.