prisma-cli

Run prisma migrate dev with an optional --name flag to generate and apply a migration from your schema changes. It requires 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 tracking history, making it suited for prototyping and MongoDB. migrate dev creates versioned migration files with drift detection and rollback capability, making it the choice for team development.

Use prisma migrate deploy, which applies pending migrations without prompts or a shadow database, making it safe for CI/CD pipelines. Check prisma migrate status first, and never run migrate dev in production.

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.

In current Prisma versions, migrate dev does not reliably emit generated client files, so run prisma generate explicitly after schema-changing commands. The same applies to db seed, which must be run separately after migrations.

Do not use it for Prisma Compute app deployment tasks such as @prisma/cli app deploy, compute:deploy, create-prisma --deploy, or managing Compute apps, logs, and domains. Those workflows belong to the prisma-compute skill instead.