adr-review

作者： prisma

以全新的視角（如同沒有先前背景的團隊成員）審查一或多個 ADR，找出敘事與結構上的問題，然後重新撰寫。適用於當…

npx skills add https://github.com/prisma/prisma-next --skill adr-review
下載 ZIPGitHub
416

Reviewing and Rewriting ADRs

Read each ADR with fresh eyes. Pretend you're a member of the team who doesn't have all the context the author has. The goal is to find places where the document assumes context the reader doesn't have, buries the decision, or carries baggage that won't make sense to a future reader.

This skill applies whether you're working on a single ADR or a batch. Treat each ADR independently — do the analysis and rewrite per document — even when several are in scope at once.

Workflow

  1. Analyze first, in chat. Before touching any file, list the issues you found and explain them. Do not rewrite silently. When multiple ADRs are in scope, group your analysis per ADR so the user can react to each one before rewrites land.
  2. Then rewrite each document to address the issues you identified.

What a good ADR looks like

  • Starts with a clear grounding example. Give the reader something concrete to pin understanding to before the abstract reasoning starts.
  • Has a strong narrative that builds the topic up bit by bit, explaining clearly throughout. Don't compress; let ideas breathe.
  • Leads with the decision. State what's being decided up front. The reader should know the conclusion before working through the reasoning.
  • Ends with alternatives considered. Put rejected options last so the reader isn't loaded down with information about paths the document is making irrelevant.

What an ADR must NOT contain

ADRs are long-lived documentation. They should not contain:

  • References to Linear tickets, GitHub issues, or other ticket trackers.
  • Milestones from the project that produced the ADR.
  • States the system passed through during or preceding a refactor that will never be seen again — interim names, deprecated wrappers being removed, "current" qualifiers, "we used to" framing.

If a piece of context only makes sense to someone who lived through the change, cut it or rewrite it as a fact about the system as it is.

Output shape

When invoked:

  1. Read the ADR (or ADRs) in scope.
  2. Write your analysis in the chat — what's missing, what's buried, what's transient, what's unclear to a fresh reader. Be specific; quote or cite the parts you're flagging. For multiple ADRs, label each block clearly.
  3. Then rewrite each file end-to-end so it follows the structure above.

來自 prisma 的更多技能

prisma-cli-migrate-reset
prisma
prisma migrate reset
official
prisma-cli-migrate-resolve
prisma
prisma migrate resolve
official
prisma-cli-studio
prisma
使用 Prisma Studio 時參考此功能。
official
prisma-cli-validate
prisma
prisma validate。使用此 Prisma 功能時的參考。
official
prisma-next-extension-upgrade
prisma
Upgrade Prisma Next in your extension. Bumps every `@prisma-next/*` dependency to the requested target (or npm `latest`), runs the per-transition upgrade…
official
prisma-next-upgrade
prisma
Upgrade Prisma Next in your app. Bumps every `@prisma-next/*` dependency from the version pinned in the lockfile to the requested target (or npm `latest`),…
official
prisma-cli
prisma
Prisma CLI 指令、選項及工作流程的完整參考，涵蓋設定、遷移與資料庫操作。包含 20 多個按優先順序組織的指令：設定（init）、生成（generate）、開發（dev）、資料庫操作（db pull/push/seed/execute）以及遷移（migrate dev/deploy/reset/status/diff/resolve）。包含 Prisma 7.x 的變更：新的 prisma.config.ts 設定檔、已移除的旗標（--skip-generate、--skip-seed、--schema、--url）以及明確...
official
prisma-client-api
prisma
完整的 Prisma Client API 參考，涵蓋模型查詢、CRUD 操作、過濾、關聯與事務。包含 17 種模型查詢方法，如 findUnique、findMany、create、update、delete、upsert 及批量操作與回傳變體。提供查詢選項以塑造結果：select、include、omit、orderBy、take、skip、cursor 與 distinct。包含標量與邏輯過濾運算子（equals、in、contains、startsWith、lt、gt）以及關聯過濾（some、...）
official