# Upgrade Prisma ORM from v6 to v7

Prisma ORM 7 changes client generation, database connections, configuration, modules, and removed APIs. This skill provides an ordered migration guide with provider-specific examples and troubleshooting.

## Install

```bash
npx skillstore add prisma/prisma-upgrade-v7
```

## Metadata

- Status: approved
- Slug: prisma-prisma-upgrade-v7
- Version: 7.6.0
- Author version: 7.6.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 9569590cf90d4f1dafd0ab859bc8d3d8941a92a39235dc01c26ef4287cf26f3e
- Author: prisma
- GitHub username: prisma
- License: MIT
- Repository: https://github.com/prisma/skills/tree/1a9f427e9fe2137298abbcc1a6f372db92e8c40d/prisma-upgrade-v7
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, env\_access, external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/prisma-prisma-upgrade-v7
- Manifest: https://skillstore.pages.dev/api/skills/prisma-prisma-upgrade-v7/manifest

## Capabilities

- Explains the main breaking changes between Prisma ORM 6 and 7.
- Shows how to configure the prisma-client generator and explicit output paths.
- Provides driver adapter examples for supported SQL databases.
- Covers Prisma configuration and explicit environment variable loading.
- Explains ESM defaults and the CommonJS generator option.
- Maps removed middleware, metrics, and CLI behavior to current alternatives.

## Use Cases

- Upgrade a backend service: Follow an ordered checklist for generator, adapter, configuration, import, and client changes.
- Standardize platform configuration: Compare adapter, environment, module, and deployment requirements across several services.
- Plan migration work: Identify breaking changes, operational risks, and verification tasks before scheduling an upgrade.

## Prompt Templates

### Review my upgrade

```
Review my Prisma 6 project structure and list the required Prisma 7 changes in order. Explain each change before suggesting edits.
```

### Update the generator

```
Help me replace prisma-client-js with prisma-client. Choose an output path that matches my project structure and update the related imports.
```

### Configure my adapter

```
Migrate my database connection to the correct Prisma 7 driver adapter. Preserve secure TLS and pool settings for my deployment environment.
```

### Audit the full migration

```
Audit this Prisma 7 migration for module compatibility, removed APIs, environment loading, generated entrypoints, connection security, and destructive commands. Propose focused tests.
```

## Limitations

- The guidance targets Prisma ORM 7.6.0 and may not reflect later releases.
- MongoDB projects require a separate migration path because Prisma ORM 7 lacks a MongoDB connector.
- Examples require adaptation for each project layout, provider, runtime, and deployment environment.
- Execution depends on the host agent and user permissions; the skill does not guarantee a successful migration.

## Best Practices

- Inspect the provider, runtime, module format, and project layout before changing files.
- Use verified TLS certificates and keep credentials in managed environment variables.
- Back up data and run generation, type checks, migrations, and application tests in a nonproduction environment.

## Anti Patterns

- Do not apply the SQL adapter workflow to MongoDB projects.
- Do not disable certificate verification to resolve production TLS errors.
- Do not run forced reset or migration commands before confirming the target database and backup status.

## Security Audit

- Audited at: 2026-07-23T18:05:53.076\+00:00
- Summary: All 268 static findings are false positives caused by documentation examples, Markdown syntax, fixed paths, environment placeholders, and official links. Three semantic findings remain: disabled TLS verification, unredacted query-argument logging, and an unguarded forced database reset. The skill shows no prompt injection, credential exfiltration, or hidden executable payload.

## Stats

- Views: 0
- Downloads: 6
- Favorites: 0
- Popularity score: 0