adr-review

作成者： prisma

1つ以上のADRを新たな視点で（事前知識のないチームメンバーとして）レビューし、ナラティブや構造上の問題を特定した上で、それらを書き直します。以下の場合に使用します…

npx skills add https://github.com/prisma/prisma-next --skill adr-review
ZIPダウンロードGitHub
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。このPrisma機能を使用する際の参考情報。
official
prisma-cli-validate
prisma
prismaのバリデーション。この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操作、フィルタリング、リレーション、トランザクションに対応。findUnique、findMany、create、update、delete、upsert、バルク操作とその戻り値バリアントを含む17のモデルクエリメソッドを網羅。結果を整形するためのクエリオプション（select、include、omit、orderBy、take、skip、cursor、distinct）を提供。スカラーおよび論理フィルター演算子（equals、in、contains、startsWith、lt、gt）に加え、リレーションフィルター（some、...）を含む。
official