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 explicitly afterward when you need refreshed client output.

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 and is the correct choice for team development and production-bound changes.

Yes, but you must add the --bun flag so Prisma runs with the Bun runtime instead of falling back to Node.js due to the CLI shebang. Use bunx --bun prisma init and bunx --bun prisma generate.

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 obtain consent immediately before running the command.

Use prisma migrate deploy, which applies pending migrations without prompts or shadow databases and is safe for CI/CD pipelines. Never use migrate dev in production, and check prisma migrate status first to verify pending migrations.

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