prisma-cli

To run Prisma migrations and generate the client, apply schema changes using `prisma migrate dev` or `prisma migrate deploy`, then execute `prisma generate` to synchronize your database schema and client types.

The best way to synchronize a Prisma schema with an existing database is using `prisma db pull` for introspection to extract the current schema, or `prisma db push` to apply schema changes directly without creating migration history, ideal for rapid prototyping.

To fix Prisma migration drift or reset database state, use `prisma migrate reset` to drop and recreate the database from scratch, or apply `prisma migrate resolve` to mark failed migrations as rolled back or applied, recovering your workflow without manual SQL intervention.

Yes, you can execute raw SQL and seed your database using Prisma CLI commands. The CLI supports raw SQL execution for direct database operations and provides `prisma db seed` to populate your database with initial data based on your seed script configuration.

You should use `prisma db push` instead of `prisma migrate dev` when you need to quickly synchronize schema changes during prototyping without generating migration files. Use `migrate dev` for production-like environments requiring versioned migration history and drift checking.

Yes, Prisma CLI supports debugging and MCP commands for the 7.x version. The command reference covers operational details for tooling, including introspection, schema synchronization, resets, recovery workflows, and Prisma MCP integration for advanced database operations.