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/migrate-deploy.md

View on GitHub
# prisma migrate deploy

Applies pending migrations in production/staging environments.

## Command

```bash
prisma migrate deploy
```

## What It Does

- Applies all pending migrations from `prisma/migrations/`
- Updates `_prisma_migrations` table
- Does NOT generate new migrations
- Does NOT run seed scripts
- Safe for CI/CD and production

## Options

| Option     | Description                            |
| ---------- | -------------------------------------- |
| `--schema` | Custom path to your Prisma schema      |
| `--config` | Custom path to your Prisma config file |

## When to Use

- Production deployments
- Staging environments
- CI/CD pipelines
- Any non-development environment

## Examples

### Basic deployment

```bash
prisma migrate deploy
```

### In CI/CD pipeline

```yaml
# GitHub Actions example
- name: Apply migrations
  run: npx prisma migrate deploy
  env:
      DATABASE_URL: ${{ secrets.DATABASE_URL }}
```

### Docker deployment

```dockerfile
# Run migrations before starting app
CMD npx prisma migrate deploy && node dist/index.js
```

## Comparison with migrate dev

| Feature              | migrate dev | migrate deploy |
| -------------------- | ----------- | -------------- |
| Creates migrations   | Yes         | No             |
| Applies migrations   | Yes         | Yes            |
| Detects drift        | Yes         | No             |
| Prompts for input    | Yes         | No             |
| Uses shadow database | Yes         | No             |
| Safe for production  | No          | Yes            |
| Resets on issues     | Prompts     | Fails          |

## Production Workflow

1. **Development**: Create migrations locally

    ```bash
    prisma migrate dev --name add_feature
    ```

2. **Commit**: Include migration files in version control

    ```bash
    git add prisma/migrations
    git commit -m "Add feature migration"
    ```

3. **Deploy**: Apply in production
    ```bash
    prisma migrate deploy
    ```

## Error Handling

### Failed migration

If a migration fails, `migrate deploy` exits with error. The failed migration is marked as failed in `_prisma_migrations`.

To fix:

1. Resolve the issue (fix SQL, database state, etc.)
2. Mark as resolved: `prisma migrate resolve --applied <migration_name>`
3. Re-run: `prisma migrate deploy`

### Check status first

```bash
prisma migrate status
```

Shows pending and applied migrations before deploying.

## Configuration

Ensure `prisma.config.ts` has the production database URL:

```typescript
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'

export default defineConfig({
    datasource: {
        url: env('DATABASE_URL'),
    },
})
```

## Best Practices

1. Always run `migrate status` before `migrate deploy` in CI
2. Have a rollback plan (backup before migrations)
3. Test migrations in staging first
4. Never use `migrate dev` in production
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