- name
Upgrade a PostgreSQL app from Prisma ORM 6 or 7 straight to Prisma 8 in one pass, keeping the existing schema.prisma, database and data. Use when a Postgres project on Prisma 6 or 7 wants Prisma 8, in
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add prisma/skills --skill prisma-postgres-upgrade -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add prisma/skills --skill prisma-postgres-upgrade -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add prisma/skills --skill prisma-postgres-upgrade -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add prisma/skills --skill prisma-postgres-upgrade -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/prisma/skills/tree/HEAD/prisma-postgres-upgradeFrom the publisher
Move a Node.js server on Prisma ORM 6 or 7 and PostgreSQL to Prisma 8 in one pass. The schema, the database and its data stay, and the app keeps running wherever it runs today.
This skill is the bridge. It covers only what is specific to leaving Prisma ORM 6 or 7. Prisma 8
itself (the contract, migrations, queries, errors) is covered by the prisma-8 skill that ships
inside @prisma/orm-postgres, which step 2 installs. Follow it for anything Prisma 8 specific;
it matches the installed version, and this skill does not.
prisma-8 says it does not apply to a project that still has schema.prisma and
@prisma/client. That is expected mid-upgrade: this skill keeps both until step 5, and
prisma7Schema(...) reads that schema.prisma. Use prisma-8 for the Prisma 8 side anyway.
The Prisma ORM 6 or 7 to 8 (PostgreSQL) guide is the source of truth for the steps.
Never do either of these:
schema.prisma unchanged, so prisma-upgrade-v7 is only for apps that stay on 7.prisma@latest or @prisma/orm-postgres@latest when the app will deploy on
Prisma Compute: the latest pair does not work with the Composer version the Console's setup
installs, so the deploy fails.prisma-computeNot for: deploying on Compute (use prisma-compute, deploy-existing-app), MongoDB (use
prisma-mongodb-upgrade), a Prisma ORM 7 app moving one route at a time beside Prisma 8
(follow the route-by-route guide),
a project already on Prisma 8 (use the synced prisma-8 skill), or a new project (use
prisma-orm-setup).
Install exact versions with --save-exact. For an app headed to Compute, use the versions the
Console's setup uses: today prisma 8.0.0-rc.27 (dev dependency) and @prisma/orm-postgres
8.0.0-rc.20. If the Console's message or an existing setup pull request names other versions,
use those. Use Node.js 24.11 or newer if the app will run under prisma dev.
In step 1, also remove prisma generate from build, postinstall and any other script: the
Prisma 8 CLI has no generate and fails with CLI.UNKNOWN_COMMAND. Step 1 removes the only
command that generated the old client. It keeps working locally, but a fresh install (CI, a new
clone) has none, so finish step 4 before pushing to a branch CI builds.
The sync in step 2 installs prisma-8, prisma-platform-core-concepts and
prisma-composer-core-concepts in one go, because the CLI depends on Composer. It writes them
for every agent it knows unless skills.agents in the config lists only the ones the repository
uses. In a Prisma ORM 7 app, replace the old prisma.config.ts before syncing: the sync fails
with CLI.CONFIG_UNREADABLE while the old one is in place.
Commit what Prisma 8 writes: src/prisma/contract.json, src/prisma/contract.d.ts and the
whole migrations/ folder. There is no generate step to recreate them in CI.
In step 5, npm uninstall @prisma/client leaves the generated client behind; delete
node_modules/.prisma too, then run a fresh install and the checks so nothing still imports it.
When the upgrade is done and the checks pass, deploy with the prisma-compute skill
(references/deploy-existing-app.md). Compute runs only Prisma 8, so the upgrade has to be
finished first.
The agent cannot do these; stop and ask:
client-api-mapping).npx prisma db sign. The agent
has only the local one.A Prisma ORM 6.19 app (Express 4, EJS, tsc, CommonJS) on PostgreSQL 18, with prisma
8.0.0-rc.27 and @prisma/orm-postgres 8.0.0-rc.20. Two agents with no context and only these
skills upgraded it: pages and API output were identical before and after against the same
database, and prisma db verify passed.
Once the app runs on Prisma 8, use the synced prisma-8 skill for day-to-day work and
prisma-compute to deploy and operate it on Compute. This skill covers the upgrade only.
© 2026 Skills Rack.
---name: prisma-postgres-upgradedescription: Upgrade a PostgreSQL app from Prisma ORM 6 or 7 straight to Prisma 8 in one pass, keeping the existing…---# prisma-postgres-upgrade/SKILL.mdOverview
Upgrade a PostgreSQL app from Prisma ORM 6 or 7 straight to Prisma 8 in one pass, keeping the existing schema.prisma, database and data. Use when a Postgres project on Prisma 6 or 7 wants Prisma 8, including before deploying it on Prisma Compute, which runs only Prisma 8. Triggers on "upgrade prisma 6 to 8", "upgrade prisma 7 to 8", "upgrade to prisma 8 postgres", "prisma7Schema", "migrations/app", "move off @prisma/client", "Console says move to Prisma 8".
FAQ
Download prisma-postgres-upgrade/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/prisma/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.