adr-review
par prisma
Examiner un ou plusieurs ADR avec un regard neuf (en tant que membre de l’équipe sans contexte préalable), identifier les problèmes narratifs et structurels, puis les réécrire. À utiliser lorsque le…
npx skills add https://github.com/prisma/prisma-next --skill adr-reviewReviewing 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
- 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.
- 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:
- Read the ADR (or ADRs) in scope.
- 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.
- Then rewrite each file end-to-end so it follows the structure above.
Plus de skills de prisma
prisma-cli-migrate-reset
prisma
prisma migrate reset
official
prisma-cli-migrate-resolve
prisma
prisma migrate resolve
official
prisma-cli-studio
prisma
Studio Prisma. Référence lors de l'utilisation de cette fonctionnalité Prisma.
official
prisma-cli-validate
prisma
Validation Prisma. Référence lors de l'utilisation de cette fonctionnalité 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
We need to translate the given text from English to French, preserving the name "prisma-cli" and other technical terms. The text is a description of a directory item for an agent skill. We must not add any extra commentary, labels, or formatting. Just the translation. The text: "Complete reference for Prisma CLI commands, options, and workflows across setup, migrations, and database operations. Covers 20+ commands organized by priority: setup ( init ), generation ( generate ), development ( dev ), database operations ( db pull/push/seed/execute ), and migrations ( migrate dev/deploy/reset/status/diff/resolve ) Includes Prisma 7.x changes: new prisma.config.ts configuration file, removed flags ( --skip-generate , --skip-seed , --schema , --url ), and explicit..." We need to translate into French. Keep technical terms like "Prisma CLI", "init", "generate", "dev", "db pull/push/seed/execute", "migrate dev/deploy/reset/status/diff/resolve
official
prisma-client-api
prisma
Référence complète de l'API Prisma Client pour les requêtes de modèle, les opérations CRUD, le filtrage, les relations et les transactions. Couvre 17 méthodes de requête de modèle, dont findUnique, findMany, create, update, delete, upsert et les opérations en masse avec variantes de retour. Fournit des options de requête pour façonner les résultats : select, include, omit, orderBy, take, skip, cursor et distinct. Inclut les opérateurs de filtre scalaires et logiques (equals, in, contains, startsWith, lt, gt) ainsi que les filtres de relation (some,...
official