prisma-cli

Generate accurate Prisma 7.6.0 CLI commands for migrations, database sync, and client generation.

1|Updated May 1, 2026
One-click install
npx skills add https://github.com/Joshkovu/ghost-ai --skill prisma-cli-joshkovu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-cli
Source: https://github.com/Joshkovu/ghost-ai/tree/main/.agents/skills/prisma-cli
Command: npx skills add https://github.com/Joshkovu/ghost-ai --skill prisma-cli-joshkovu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prisma CLI command knowledge is scattered across flags, versions, and docs, making it hard to run setup, migrations, database sync, and tooling steps correctly and consistently.

Core Features & Use Cases

  • Prisma project setup: Use init to bootstrap schema, config, and common Prisma layout.
  • Client generation: Generate typed Prisma Client after schema changes so your app stays in sync.
  • Database lifecycle management: Run migrations (dev/deploy), sync schema directly (db push), inspect existing DB (db pull), manage resets, and seed data.
  • Tooling & developer workflows: Use studio for inspection and mcp for AI-tool integration, plus validate/format/debug for correctness and troubleshooting.
  • Use case: When evolving a production system, you can safely create migrations in development, verify status, then apply them in CI/CD using the exact command patterns for your Prisma release.

Quick Start

Use this skill to generate the exact Prisma CLI command for the workflow you need, then apply it to your project in the right order (init/generate/migrate/db/seed/studio/mcp).

Frequently Asked Questions about prisma-cli

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

FAQPage Schema
How do I run Prisma migrations correctly in a production deployment workflow?

Prisma migrations in production use the migrate deploy command to apply pending schema files safely. This ensures synchronized database state during CI/CD pipeline deployments without interactive development prompts.

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

Prisma db push synchronizes your schema directly to the database without creating migration history, making it ideal for prototyping. Prisma migrate dev generates migration files and tracks schema changes for reproducible production deployments.

How do I generate the Prisma client after updating my database schema?

Generate the Prisma client after schema changes by running the prisma generate command. This updates your typed client to match the current schema, ensuring your application code stays synchronized with your database models.

Can I use Prisma MCP for AI tooling integration and database management?

Yes, Prisma MCP enables AI tooling integration by exposing database management capabilities to AI assistants. This allows compatible tools to inspect schemas, execute raw SQL, and interact with your Prisma setup programmatically.

How do I inspect and pull an existing database schema into a new Prisma project?

Pull an existing database schema into Prisma using the db pull command. This introspects your database and automatically generates the schema.prisma file, allowing you to bootstrap ORM models from an established database.

What Prisma CLI commands are available for troubleshooting schema validation errors?

For troubleshooting schema validation errors, Prisma CLI provides the validate command to check schema correctness, format to standardize file syntax, and debug to output detailed diagnostic information for resolving configuration issues.