prisma-cli

Run prisma migrate dev --name your_migration_name to create and apply a migration from schema changes. Afterwards, run prisma generate explicitly to refresh the client and prisma db seed if you need seed data.

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

Use prisma migrate deploy in production, staging, and CI/CD pipelines. It applies pending migrations without prompts or shadow databases. Never use migrate dev in production environments.

Prisma detects AI agents 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.

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

Use db pull to introspect an existing database and generate a Prisma schema from its structure. It is ideal when adopting Prisma on a legacy database, but it overwrites your schema file, so preview with --print first.