prisma-cli

Consolidate Prisma 7 CLI workflows for init, generate, migrate, and db commands.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/JoeKarow/motw-campaign-tracker --skill prisma-cli-joekarow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-cli
Source: https://github.com/JoeKarow/motw-campaign-tracker/tree/main/.agents/skills/prisma-cli
Command: npx skills add https://github.com/JoeKarow/motw-campaign-tracker --skill prisma-cli-joekarow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill conquers the challenge of remembering Prisma 7 CLI flags and workflows by providing a single reference for initialization, generation, migrations, database management, and utility commands.

Core Features & Use Cases

  • Priority command guidance: Organized command categories let you immediately choose the right flow for setup, generation, development, database operations, migrations, or utilities such as studio and debug.
  • Detailed command references: Each referenced document explains syntax, options, examples, and Prisma 7 changes for prisma init, prisma generate, prisma migrate, prisma db, prisma dev, and other commands.
  • Practical workflows: Use the curated notes to determine when to run prisma migrate dev, prisma migrate deploy, prisma db push, or prisma migrate diff and how to keep dotenv configuration, seed scripts, and explicit generate steps aligned with best practices.

Quick Start

Use the prisma-cli skill to outline how to run prisma migrate dev followed by prisma generate in a Prisma 7 project.

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 in a development environment?

Use prisma migrate dev during development to apply schema changes and generate the client. For deployment scenarios without a migration history, use prisma db push to sync the database schema directly.

What is the correct Prisma 7 workflow for initializing a new database project?

The Prisma 7 initialization workflow starts with prisma init to create the schema and dotenv configuration. After defining your models, run prisma migrate dev to create the database and prisma generate to produce the client.

When should I use prisma migrate deploy instead of prisma migrate dev?

Use prisma migrate deploy in production or CI environments to apply pending migration files without resetting data. Use prisma migrate dev only in development, as it can trigger data loss when resetting the database after schema drift.

Do I need to run prisma generate separately after updating my schema?

Yes, running prisma generate explicitly is required in Prisma 7 to update the client types after schema changes. Commands like prisma migrate dev may trigger it, but explicit generation ensures your client matches the latest schema.

How does Prisma CLI handle dotenv configuration for database connections?

Prisma CLI relies on dotenv configuration to load environment variables like DATABASE_URL. Ensure your .env file is properly configured before running prisma init, prisma migrate, or prisma db commands to avoid connection errors.

Can I use Prisma Studio to manage my database records during development?

Yes, Prisma Studio is accessible via the prisma studio command and provides a visual interface to view and edit database records. It is categorized as a utility command for development workflows in Prisma 7.