Skip to content

NarixHine/uni-chem / .agents/skills/prisma-cli

prisma-cli

Verified

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, studio, validate, format, debug, and mcp. Use for ORM/database CLI workflows, not Prisma Compute app deployment. For Prisma Compute, `@prisma/cli app deploy`, `compute:deploy`, `create-prisma --deploy`, apps, deployments, logs, or domains, use the `prisma-compute` skill instead. Triggers on "prisma init", "prisma generate", "prisma migrate", "prisma db", "prisma studio", "prisma mcp".

FileKindSize
SKILL.mdskill md7.6 KB
references/db-execute.mdmarkdown1.9 KB
references/db-pull.mdmarkdown4.1 KB
references/db-push.mdmarkdown3.1 KB
references/db-seed.mdmarkdown3.5 KB
references/debug.mdmarkdown1.1 KB
references/dev.mdmarkdown2.8 KB
references/format.mdmarkdown1.1 KB
references/generate.mdmarkdown3.7 KB
references/init.mdmarkdown3.5 KB
references/mcp.mdmarkdown1.1 KB
references/migrate-deploy.mdmarkdown2.8 KB
references/migrate-dev.mdmarkdown3.4 KB
references/migrate-diff.mdmarkdown2.2 KB
references/migrate-reset.mdmarkdown1.6 KB
references/migrate-resolve.mdmarkdown1.8 KB
references/migrate-status.mdmarkdown1.6 KB
references/studio.mdmarkdown2.9 KB
references/validate.mdmarkdown964 B

references/db-push.md

View on GitHub
# prisma db push

Pushes schema changes directly to database without creating migrations. Ideal for prototyping.

## Command

```bash
prisma db push [options]
```

## What It Does

- Syncs your Prisma schema to the database
- Creates database if it doesn't exist
- Does NOT create migration files
- Does NOT track migration history

## Options

| Option               | Description                                             |
| -------------------- | ------------------------------------------------------- |
| `--force-reset`      | Force a reset of the database before push               |
| `--accept-data-loss` | Ignore data loss warnings                               |
| `--schema`           | Custom path to your Prisma schema                       |
| `--config`           | Custom path to your Prisma config file                  |
| `--url`              | Override the datasource URL from the Prisma config file |

### Follow-up Command

- Run `prisma generate` explicitly when you need refreshed client output

## Examples

### Basic push

```bash
prisma db push
```

### Accept data loss

```bash
prisma db push --accept-data-loss
```

Required when changes would delete data (dropping columns, etc.)

### Force reset

```bash
prisma db push --force-reset
```

Completely resets database and applies schema.

### Full workflow

```bash
prisma db push
prisma generate
```

## When to Use

- **Prototyping** - Rapid schema iteration
- **Local development** - Quick schema changes
- **MongoDB** - Primary workflow (migrations not supported)
- **Testing** - Setting up test databases

## When NOT to Use

- **Production** - Use `migrate deploy`
- **Team collaboration** - Use migrations for trackable changes
- **When you need rollback** - Migrations provide history

## Comparison with migrate dev

| Feature                  | db push     | migrate dev |
| ------------------------ | ----------- | ----------- |
| Creates migration files  | No          | Yes         |
| Tracks history           | No          | Yes         |
| Requires shadow database | No          | Yes         |
| Speed                    | Faster      | Slower      |
| Rollback capability      | No          | Yes         |
| Best for                 | Prototyping | Development |

## MongoDB Workflow

MongoDB doesn't support migrations. Use `db push` exclusively:

```bash
# Schema changes for MongoDB
prisma db push
prisma generate
```

## Common Patterns

### Prototyping workflow

```bash
# Make schema changes
# ...

# Push to database
prisma db push

# Generate client
prisma generate

# Test your changes
# Repeat as needed
```

### Reset and start fresh

```bash
prisma db push --force-reset
prisma db seed
```

### Handling conflicts

If `db push` can't apply changes safely:

```
Error: The following changes cannot be applied:
  - Removing field `email` would cause data loss

Use --accept-data-loss to proceed
```

Decide whether data loss is acceptable, then:

```bash
prisma db push --accept-data-loss
```

## Transition to Migrations

When ready for production, switch to migrations:

```bash
# Create baseline migration from current schema
prisma migrate dev --name init
```

Then use `migrate dev` for future changes.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall