Index of every page on this site: llms.txt
All skills
prisma avatar

/prisma-postgres-upgrade

@a6f1929 official
by prismaprisma/skills80 stars
8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/prisma/skills/prisma-postgres-upgrade

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesverify-upgrade-checklist.md

≈668 tokens on demand. Your agent reads this file only when SKILL.md points to it.

verify-upgrade-checklist

Prove the upgrade with the repository's own checks, run the same way before and after.

Priority

CRITICAL

Why It Matters

A query rewrite can compile and still return different data, or fail only at runtime. The only evidence the user can trust is the project's existing checks passing on both sides of the change. Checks the agent writes for itself prove only what the agent expected.

Rules

  • Use what the repo has. Find the type check, build, lint and test scripts in package.json and CI config, and run exactly those.
  • Same commands before and after. Record each command and its result before step 1. Run the identical commands after step 5. A check that was already failing before is reported as such, not fixed silently.
  • Do not invent checks. Do not write or commit new tests or smoke scripts to stand in for missing ones, and do not change existing tests to make them pass.
  • Comparing pages by hand is fine, and it is not a test. Requesting a few read-only pages before and after, against the same database, catches templates tsc never checks. Report it as a manual comparison, never as test coverage.
  • No tests? Say so. If the repository has no tests, tell the user plainly that the upgrade is verified only by type check, build and the app starting, and leave the change for them to review before it ships.

Checklist

  1. Baseline: run the type check (tsc --noEmit or the repo's script), the build, and the test script, then start the app with its own start command and confirm it boots and connects. Record SHOW timezone on the database.
  2. After step 4: same commands, against the same local database. No file imports @prisma/client or the generated client.
  3. After step 5: a fresh install, then the same commands as the baseline, plus npx prisma db verify against the signed database. Start the app with its own start command again.
  4. Report: each command, before and after, pass or fail. List what was not verified, including any behavior the tests do not cover, including the rc.20 DateTime and now() notes in client-api-mapping.md. If the database's time zone is not UTC, say so first: new rows store a different time than before.

Bad

"Added tests/upgrade.test.ts that hits every route; all pass."

Good

Before: tsc ok, build ok, npm test 42 passed. After: tsc ok, build ok, npm test 42 passed,
app starts. Not verified: behavior the tests do not cover.

References

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts11d3 checks · Risk SAFE
  • Gen Agent Trust Hub11d

    The skill provides a legitimate and well-documented workflow for upgrading applications from Prisma ORM 6 or 7 to Prisma 8. It adheres to security best practices by using environment variables for database credentials and relying on official vendor tools and packages. No malicious behavior or security vulnerabilities were detected.

  • Socket11d

    No alerts

  • Snyk11d

    Risk: LOW · No issues

Signed by skilld at a6f1929. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago
metadata
{
  "author": "prisma",
  "version": "2.0.0"
}

README badge

README badge for prisma/skills/prisma-postgres-upgrade