Prisma Cli

Prisma CLI is a community skill for managing databases using the Prisma command-line interface, covering schema authoring, migration management, database introspection, seed scripts, and studio access for database workflow automation.

What Is This?

Overview

Prisma CLI provides patterns for managing database schemas and migrations using the Prisma toolkit. It covers schema file authoring with model definitions, relations, and field attributes for type-safe database modeling, migration creation and application with prisma migrate for version-controlled schema changes, database introspection with prisma db pull for generating schemas from existing databases, seed script execution for populating databases with test and development data, and Prisma Studio launch for visual database browsing and editing. The skill enables developers to manage their database lifecycle from schema design through production deployment using the Prisma CLI toolchain.

Who Should Use This

This skill serves backend developers managing database schemas with Prisma ORM, teams running database migrations in CI/CD pipelines, and developers introspecting existing databases to generate Prisma schemas automatically. It is also well suited for full-stack developers who need a consistent, repeatable database workflow across local, staging, and production environments.

Why Use It?

Problems It Solves

Writing raw SQL migrations manually is error-prone and difficult to track across environments. Generating type-safe database client code requires keeping schema definitions synchronized with the actual database. Populating test databases with realistic seed data needs repeatable scripts that can be run consistently by every team member. Visualizing database contents for debugging requires external tools.

Core Highlights

Migration engine creates SQL migrations from schema diffs with rollback support. Introspection generates Prisma schema files from existing database structures, making it straightforward to adopt Prisma on legacy projects. Client generator produces type-safe query builders from schema definitions. Studio provides a visual interface for browsing and editing database records.

How to Use It?

Basic Usage

npx prisma init
  --datasource-provider postgresql

npx prisma migrate dev \
  --name add_users_table

npx prisma generate

npx prisma db pull

npx prisma studio

npx prisma db seed

npx prisma migrate reset

npx prisma migrate deploy

npx prisma migrate status

Real-World Examples

// prisma/schema.prisma content
// as TypeScript seed script
// prisma/seed.ts
import { PrismaClient } from
  '@prisma/client';

const prisma = new PrismaClient();

async function main() {
  const admin = await prisma.user
    .upsert({
      where: {
        email: 'admin@example.com' },
      update: {},
      create: {
        email: 'admin@example.com',
        name: 'Admin User',
        role: 'ADMIN',
        posts: {
          create: [
            { title: 'First Post',
              slug: 'first-post',
              content: 'Hello world',
              published: true },
            { title: 'Draft Post',
              slug: 'draft-post',
              content: 'Work in '
                + 'progress',
              published: false },
          ],
        },
      },
    });
  console.log({ admin });

  const users = await prisma.user
    .createMany({
      data: Array.from(
        { length: 10 },
        (_, i) => ({
          email: `user${i}@example.com`,
          name: `User ${i}`,
          role: 'USER',
        })),
      skipDuplicates: true,
    });
  console.log(
    `Created ${users.count} users`);
}

main()
  .catch(console.error)
  .finally(() => prisma.$disconnect());

Advanced Tips

Use prisma migrate diff to compare schema states and generate custom migration SQL for complex changes such as column renames or data transformations that require manual handling. Configure the seed command in package.json to run TypeScript seed files with ts-node. Use prisma validate to check schema syntax before running migrations in CI pipelines. Additionally, use the --skip-generate flag with prisma migrate deploy in production to avoid regenerating the client unnecessarily when it has already been built during the CI step.

When to Use It?

Use Cases

Build a CI/CD pipeline that runs prisma migrate deploy to apply pending migrations during deployment. Create a development setup script that resets the database and seeds it with test data. Implement a schema evolution workflow where each feature branch creates its own migration file.

Related Topics

Database migrations, ORM tooling, schema management, database seeding, and development workflow automation.

Important Notes

Requirements

Node.js with Prisma CLI installed as a dev dependency. A supported database such as PostgreSQL, MySQL, or SQLite. Connection string configured in the schema.prisma datasource block.

Usage Recommendations

Do: commit migration files to version control for consistent schema changes across team environments. Use prisma migrate dev during development and prisma migrate deploy for production. Run prisma generate after every schema change to update the client.

Don't: manually edit generated migration SQL files unless adding data migrations that Prisma cannot generate. Run prisma migrate reset in production as it drops and recreates the database. Skip running prisma migrate status in CI to catch unapplied migrations.

Limitations

Prisma migrate does not support down migrations for automatic rollback of applied changes. Some database features like partial indexes or custom types require raw SQL in migrations. The introspection tool may not perfectly map all database-specific features to the Prisma schema.