New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

ADR Review

by prisma in prisma/orm

Reviews architecture decision records as a reader with no prior context, reports what is unclear or buried in chat, then rewrites each ADR to lead with the decision.

OfficialApache-2.0Auto-check passedDevelopment

Install ADR Review

skills CLI
$ npx skills add prisma/orm --skill adr-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install prisma/orm adr-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/prisma/orm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills-contrib/adr-review .claude/skills/adr-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
adr-review
GitHub stars
48k
Token cost
~672 tokens
SKILL.md length
380 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reviews architecture decision records as a reader with no prior context, reports what is unclear or buried in chat, then rewrites each ADR to lead with the decision.

  • Works in 2 steps: Analyze first, in chat. Before touching… → Then rewrite each document to address…
  • Giving a draft architecture decision record a fresh-eyes review
  • SKILL.md covers Workflow, What a good ADR looks like, What an ADR must NOT contain and Output shape
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The agent reads each ADR as a teammate who lacks the author's background and looks for places that assume knowledge, hide the decision or carry baggage a future reader will not understand. Analysis comes first, in chat and grouped per ADR when several are in scope, with every issue listed and explained before any file is changed.

Rewrites then follow a target shape: a concrete example up front, a narrative that builds the topic gradually, the decision stated early and rejected alternatives placed last. ADRs should not point to Linear tickets, GitHub issues, project milestones or transitional states such as interim names and we-used-to framing, so the skill cuts those or restates them as facts about the system as it is.

When your agent uses it

  • Giving a draft architecture decision record a fresh-eyes review
  • Rewriting a batch of ADRs so each one leads with its decision
  • Cleaning ticket links and project milestones out of long-lived design docs
  • Checking whether a new teammate could follow an ADR without extra context

Example prompts

  • “Review docs/adr/queue-backend.md as if you just joined the team, then rewrite it.”
  • “Take a fresh-eyes pass over every ADR in docs/decisions and tell me what is buried before changing anything.”
  • “Remove the ticket references and the we-used-to wording from this ADR.”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Analyze first, in chat. Before touching any file, list the issues you found and explain them. Do not rewrite silently. When multiple ADRs…
  2. Then rewrite each document to address the issues you identified.

What it can do on your machine

Read from SKILL.md and the folder at commit 6e12cc2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

ADR Review loads about 672 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 380 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~672

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from prisma/orm at commit 6e12cc2, republished under its Apache-2.0 licence (© prisma). 380 words, ~672 tokens.

Download SKILL.mdSave it as .claude/skills/adr-review/SKILL.md (or your agent's skills folder).
name
adr-review
description
Review one or more ADRs with fresh eyes (as a team member without prior context), identify narrative and structural issues, then rewrite them. Use when the user asks to review, improve, rewrite, or take a fresh-eyes pass on an ADR or a set of ADRs (Architecture Decision Records).

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.
Show full SKILL.md (148 more words)Show less

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, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills-contrib/adr-review of prisma/orm.

Open the folder on GitHubat commit 6e12cc2

Compare with similar skills

ADR Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

ADR Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
ADR Review this skillprisma/orm48k—~672Automated safety check: PassApache-2.0
Docsbrickbots/PiFinder250—~6.2kAutomated safety check: PassGPL-3.0
Evidence-Backed Documentation Writerbgauryy/octocode949—~2kAutomated safety check: PassMIT
Write Vibe ADRmistralai/mistral-vibe5.1k—~942Automated safety check: PassApache-2.0
Technical Documentation Templatesbybren-llc/safe-agentic-workflow423—~1.2kAutomated safety check: PassMIT
Agent Stylepchalasani/claude-code-tools2k—~1.4kAutomated safety check: PassMIT

Similar skills

  • Docs

    brickbots/PiFinder

    Author and edit PiFinder's user-facing documentation in the project's house style.

    250 GitHub stars~6.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Evidence-Backed Documentation Writer

    bgauryy/octocode

    Writes, repairs and copyedits project docs against the Google developer documentation style guide, verifying claims in the repository before stating them.

    949 GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Write Vibe ADR

    mistralai/mistral-vibe

    Official

    Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table.

    5.1k GitHub stars~942 tokensUpdated today
    DevelopmentAuto-check passed

  • Technical Documentation Templates

    bybren-llc/safe-agentic-workflow

    Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing…

    423 GitHub stars~1.2k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Agent Style

    pchalasani/claude-code-tools

    Literature-backed English technical-prose writing rules (agent-style, 21 rules).

    2k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Gentle AI Cognitive Doc Design

    Gentleman-Programming/gentle-shell

    Design docs that reduce cognitive load. An agent skill from Gentleman-Programming/gentle-shell.

    1.3k GitHub stars~597 tokensUpdated today
    DevelopmentAuto-check passed

More from prisma/orm

All 20 skills in this repo

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    Auto-check passed

  • Review Implement Phase

    prisma/orm

    Official

    Implements triaged pull request review actions, commits focused fixes, posts status replies on GitHub and resolves the threads.

    48k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Review Triage Phase

    prisma/orm

    Official

    Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.

    48k GitHub stars~995 tokensUpdated today
    Auto-check passed

  • AST Visitor Pattern for Unions

    prisma/orm

    Official

    Replaces a plain TypeScript union plus switch statements with frozen subclasses and a visitor interface when several places dispatch on the same variants.

    48k GitHub stars~830 tokensUpdated today
    Auto-check passed

  • Prisma Contributor PR

    prisma/orm

    Official

    Guides an outside contributor through opening a prisma/orm pull request from a fork that follows CONTRIBUTING.md and passes review on the first round.

    48k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Categories

Questions about ADR Review

What does ADR Review do?

Reviews architecture decision records as a reader with no prior context, reports what is unclear or buried in chat, then rewrites each ADR to lead with the decision. The agent reads each ADR as a teammate who lacks the author's background and looks for places that assume knowledge, hide the decision or carry baggage a future reader will not understand. Analysis comes first, in chat and grouped per ADR when several are in scope, with every issue listed and explained before any file is changed.

When should I use ADR Review?

ADR Review fits situations like: giving a draft architecture decision record a fresh-eyes review; rewriting a batch of ADRs so each one leads with its decision; cleaning ticket links and project milestones out of long-lived design docs; checking whether a new teammate could follow an ADR without extra context.

How do I install ADR Review in Claude Code?

Run `npx skills add prisma/orm --skill adr-review -a claude-code`. Or copy the skill folder (skills-contrib/adr-review in prisma/orm) into .claude/skills/adr-review in your project. Claude Code loads it when a task matches its description.

How do I install ADR Review in Codex?

Run `npx skills add prisma/orm --skill adr-review -a codex`. Or copy the skill folder (skills-contrib/adr-review in prisma/orm) into .agents/skills/adr-review in your project. Codex loads it when a task matches its description.

Can I use ADR Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add prisma/orm --skill adr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adr-review, .gemini/skills/adr-review, .github/skills/adr-review and .opencode/skills/adr-review in your project.

What does ADR Review need to run?

SKILL.md names no scripts, command-line tools or credentials: ADR Review is instructions for the agent only.

Does ADR Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is ADR Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does ADR Review use?

ADR Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does ADR Review use?

About 672 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to ADR Review?

Skills that share tags, products or a category with ADR Review: Docs (brickbots/PiFinder, 250 stars), Evidence-Backed Documentation Writer (bgauryy/octocode, 949 stars), Write Vibe ADR (mistralai/mistral-vibe, 5.1k stars) and Technical Documentation Templates (bybren-llc/safe-agentic-workflow, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains ADR Review?

prisma (a GitHub organization, an official publisher) maintains it in prisma/orm, which has 47,693 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 9, 2026.

Source: prisma/orm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.