prisma-cli

Reference Prisma ORM CLI commands for migrations, client generation, and database management.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/jpmartirez/kilatis --skill prisma-cli-jpmartirez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-cli
Source: https://github.com/jpmartirez/kilatis/tree/main/frontend/.windsurf/skills/prisma-cli
Command: npx skills add https://github.com/jpmartirez/kilatis --skill prisma-cli-jpmartirez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers working with Prisma ORM often struggle to remember the correct CLI commands, flags, and workflows for tasks like running migrations, generating the client, or seeding databases, especially with behavior changes in current Prisma releases. ## Core Features & Use Cases - Command Reference: Covers the full Prisma CLI surface including init, generate, migrate, db push/pull/seed/execute, dev, studio, validate, format, debug, and mcp. - Workflow Guidance: Explains when to use db push versus migrate dev, how to handle production deployments with migrate deploy, and how to recover from failed migrations with migrate resolve. - Use Case: When setting up a new project, follow the init reference to bootstrap prisma.config.ts, start a local database with prisma dev, create migrations with migrate dev, and generate the client with the correct output configuration. ## Quick Start Ask the assistant to show how to create and apply a new Prisma migration for a schema change in the current project.

Frequently Asked Questions about prisma-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and apply a Prisma migration?

Run prisma migrate dev --name your_migration_name during development to generate and apply a migration from schema changes. For production, commit the migration files and apply them with prisma migrate deploy.

What is the difference between prisma db push and migrate dev?

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, which is better for team development.

How do I run Prisma CLI with Bun?

Prefix 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.

Does prisma migrate dev automatically generate the client?

In current Prisma releases you should run prisma generate explicitly after migrate dev, db push, or migrate reset when you need refreshed client output. The same applies to seeding, which requires an explicit prisma db seed run.

How do I fix a failed Prisma migration in production?

Resolve the underlying issue, then run prisma migrate resolve --rolled-back <migration_name> to mark it as rolled back, and re-run prisma migrate deploy. Use prisma migrate status first to inspect the current migration state.

When should I not use this Prisma CLI skill?

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