record-gotchas SKILL.md skillA

record-gotchas from prisma/orm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add prisma/orm/record-gotchas@git:20260911.1ed19e4

Pins git:20260911.1ed19e4 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
prisma/orm
Path
skills-contrib/record-gotcha/SKILL.md
Versions recorded
5
Latest version
git:20260911.1ed19e4, committed Sep 11, 2026
First version recorded
May 31, 2026
Size
22,925 bytes
Repository stars
47,691
License
Apache-2.0

Capture surprises, workarounds, and rough edges hit while *consuming* the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour while using one of these three products from the outside (extension authoring, example apps, integration tests, customer reproductions, internal demos, manual repros). Does NOT…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Record a gotcha

A **gotcha** is friction that a *consumer* of Prisma 8, Prisma Compute, or Prisma Postgres would feel — something an external user of those products would also experience: a surprising failure mode, an undocumented behaviour, a workaround you wrote, a mental model mismatch with the CLI / runtime / docs. The signal is the consumer's perspective, not the project context — you can hit a gotcha while writing an extension, working in an example app, reproducing a customer report, running an integration test against the public surface, or building anything that consumes the product from the outside.

A gotcha is **not** a bug in code your team maintains. If you own the surface and you can fix it, that's a normal product bug, filed in the regular product backlog — not a gotcha.

This skill is the canonical workflow for capturing gotchas. When the trigger fires:

1. Determine whether you're in a product-team repo or somewhere else — the escalation mode depends on it (see § Escalation mode).
2. Write a short entry to the matching gotchas log (`gotchas.md` or a per-product file).
3. File a Triage-state ticket in the matching `*-gotchas` Linear project.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ext6cf6s5ys5zm7v/ebcd563fa614c8b1271e8a02c20dbd4d396565612e72b3e74cda885b7b1a5a70.json

Then /plugin install record-gotchas@markdownregistry-ext6cf6s5ys5zm7v in Claude Code. It installs git:20260911.1ed19e4, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add prisma/orm/record-gotchas@sha256:ebcd563fa614c8b1

The line at the top of this page pins the label git:20260911.1ed19e4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_ext6cf6s5ys5zm7v.svg)](https://markdownregistry.com/a/art_ext6cf6s5ys5zm7v)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in prisma/orm/record-gotchas since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of record-gotchas from somewhere else? Ask it: where did my record-gotchas come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between May 31, 2026 and Sep 11, 2026, about one every 26 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260911.1ed19e4 latest2026-09-11 1ed19e4 22,925 BA view · diff
git:20260831.aefbf792026-08-31 aefbf79 22,949 BA view · diff
git:20260818.ac8bc452026-08-18 ac8bc45 22,918 BA view · diff
git:20260803.ada72f12026-08-03 ada72f1 22,938 BA view · diff
git:20260531.33807212026-05-31 3380721 22,977 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (22925 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

prisma/orm · 47,691 stars · license Apache-2.0 · pushed 2026-11-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ext6cf6s5ys5zm7v
GET https://markdownregistry.com/api/v1/resolve?ref=prisma/orm/record-gotchas
GET https://markdownregistry.com/api/v1/blob/ebcd563fa614c8b1271e8a02c20dbd4d396565612e72b3e74cda885b7b1a5a70

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from prisma/orm

AGENTS.md AGENTS.md file
prisma/orm · AGENTS.md
git:20261120.6f2c9bf · audit A · 47,691 stars
CLAUDE.md CLAUDE.md file
prisma/orm · CLAUDE.md
git:20260303.a55dddd · audit B · 47,691 stars
adr-review SKILL.md skill
prisma/orm · skills-contrib/adr-review/SKILL.md · Review one or more ADRs with fresh eyes (as a team member without prior context), identify narrative and structural…
git:20260517.7c3f443 · audit A · 47,691 stars
ast-visitor-pattern SKILL.md skill
prisma/orm · skills-contrib/ast-visitor-pattern/SKILL.md · Use the frozen-class/visitor pattern for discriminated unions that have multiple dispatch sites. Use when creating a…
git:20260831.aefbf79 · audit A · 47,691 stars
bumping-biome SKILL.md skill
prisma/orm · skills-contrib/bumping-biome/SKILL.md · Bumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s…
git:20260831.aefbf79 · audit A · 47,691 stars
contrib-pr SKILL.md skill
prisma/orm · skills-contrib/contrib-pr/SKILL.md · Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a…
git:20261117.45219d3 · audit A · 47,691 stars
create-pr SKILL.md skill
prisma/orm · skills-contrib/create-pr/SKILL.md · Creates a GitHub PR with a conventional-commit title and a decision-led, narrative description for Prisma 8. Use when…
git:20261111.f1e8dc5 · audit A · 47,691 stars
draft-release-notes SKILL.md skill
prisma/orm · skills-contrib/draft-release-notes/SKILL.md · Author the committed release-notes file for a Prisma 8 release (stable or `8.0.0-rc.N`) by enumerating the merged PRs…
git:20260916.f3574a3 · audit A · 47,691 stars
github-review-iteration SKILL.md skill
prisma/orm · skills-contrib/github-review-iteration/SKILL.md · Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating…
git:20260831.aefbf79 · audit A · 47,691 stars
markdown-no-artificial-line-wraps SKILL.md skill
prisma/orm · skills-contrib/markdown-no-artificial-line-wraps/SKILL.md · Writes and edits Markdown without inserting manual hard line breaks at a fixed column (e.g. 72 or 80). GitHub, docs…
git:20260517.d61853f · audit A · 47,691 stars
multiline-commit-messages SKILL.md skill
prisma/orm · skills-contrib/multiline-commit-messages/SKILL.md · Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that…
git:20260517.d61853f · audit A · 47,691 stars
no-bare-casts SKILL.md skill
prisma/orm · skills-contrib/no-bare-casts/SKILL.md · Writing `as` in TypeScript or TSX production code, modifying a file that contains a bare `as` cast, silencing a type…
git:20261021.ffa6859 · audit A · 47,691 stars

Every file in prisma/orm

Browse by kind, by grade A, or by owner.