Skills Guide

ADR Review

VerifiedCaution

Accept or reject a proposed ADR at the owner's direction, updating status, index, and log entries accordingly.

Download and use
Sby Skills Guide Bot
DocumentationIntermediate
7/23/2026
Claude CodeCodexCursor
#adr#architecture-decisions#governance#changelog#okf

Recommended for

Claude CodeCursorAuto documentationCodex

Automated summary

Drives the owner-directed acceptance or rejection of a proposed ADR, updating status, index, log, and related markers across the repo.

Strengths

  • Gives step-by-step edits for status (frontmatter and # Status section) plus index, GOAL.md milestones, and CLAUDE.md current-state updates
  • Explicitly handles rejection, reverting per the ADR's rollback trigger and running the test command afterward
  • Notes that acceptance usually requires no implementation change under the propose-then-implement policy
  • Catches legacy ADRs without frontmatter by detecting body-level status conventions

Limitations

  • Assumes okf scripts (okf pending) and files like docs/adr/index.md, docs/log.md, docs/GOAL.md exist
  • The decision belongs entirely to the owner; the assistant only performs edits on instruction
  • Does not cover drafting a new ADR or architectural design work
When to use it

Use when the owner is reviewing pending decisions and asks to accept, reject, or revise a specific ADR.

When not to use it

Avoid when the repo doesn't follow this ADR/OKF layout, or when the task is authoring a new ADR rather than ruling on an existing one.

Security analysis

Caution
Quality score82/100

This is a legitimate ADR workflow and contains no exfiltration, obfuscation, curl-pipe-shell, or absolute destructive commands. However, it directs an agent to run repository scripts, edit/delete files, and potentially revert code, so it warrants caution rather than being treated as purely non-executing.

Findings
  • •No allowed-tools are declared, but the instructions require shell execution (`bash scripts/okf pending`, repo test command) and file edits/deletions.
  • •Rejecting an ADR can revert implementation work and delete ADR files, which is potentially destructive without explicit human confirmation guardrails.
  • •The skill depends on repository-local scripts and test commands whose behavior is not specified here.
  • •It may modify multiple project files (`docs/adr/index.md`, `docs/GOAL.md`, `CLAUDE.md`, `docs/log.md`), so scope should be constrained.
How this analysis is made

Examples

Accept a pending ADR
Accept ADR-0007 at my direction — flip the status, clean up the (proposed) markers in the index and GOAL.md, and add a dated log entry.
Reject and revert
Reject ADR-0012: follow its rollback trigger section to revert the work, run the tests, and log the reversal scope.
Check what's pending
What ADRs are awaiting my review right now? Run the pending scan and summarize them.

name: okf-adr-review description: Accept or reject a proposed ADR at the owner's direction — status flip, reversal per rollback trigger, index and log updates. Use when the owner reviews pending decisions, says to accept/reject an ADR, or asks what's awaiting review.

ADR review mechanics

The owner finds pending decisions with bash scripts/okf pending (the SessionStart hook also reports the count). The decision is the owner's; the edits can be yours at their direction.

Accepting an ADR:

  1. Flip status: proposed to status: accepted in the frontmatter, and update the body # Status section (date, "at the owner's direction").
  2. Remove any "(proposed)" markers the ADR carries in the ADR index entries (docs/adr/index.md by default; a layout: block in docs/okf-map.yml may relocate it), docs/GOAL.md milestones, or the current-state line of CLAUDE.md.
  3. No implementation change is usually needed: under the propose-then-implement policy the work already exists — acceptance makes it binding for future work.
  4. Add a dated docs/log.md entry recording the acceptance, and verify bash scripts/okf pending no longer lists it.

Rejecting an ADR:

  1. Revert the work built on it, per the ADR's own rollback / revisit trigger section — that section names what reverting takes.
  2. Either delete the ADR file and its index entry, or keep it with a status: rejected note recording why, per the owner's preference.
  3. Run the repo's test command after the reversal; a broken revert is not a completed rejection.
  4. Log the rejection and the reversal scope in docs/log.md.

Requested changes (neither accept nor reject): treat the owner's comments as a task — amend the ADR and the implementation together, keep status: proposed, and flag it again in the summary.

The pending scan reads frontmatter status: first, then the body conventions brownfield repos use (a - Status: X bullet or a ## Status section). ADRs with none of those are invisible to it — add frontmatter status to them when found, as a formatting-only fix; frontmatter stays the preferred form for new ADRs.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/adr-review-mrx3xwms/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/adr-review-mrx3xwms' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/adr-review-mrx3xwms/download' --output '.skill-downloads/adr-review-mrx3xwms/SKILL.md.part' && mv '.skill-downloads/adr-review-mrx3xwms/SKILL.md.part' '.skill-downloads/adr-review-mrx3xwms/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/adr-review-mrx3xwms/SKILL.md' && test -s '.skill-downloads/adr-review-mrx3xwms/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/okf-adr-review' && cp -R '.skill-downloads/adr-review-mrx3xwms' '.claude/skills/okf-adr-review'

Cursor
test -f '.skill-downloads/adr-review-mrx3xwms/SKILL.md' && test -s '.skill-downloads/adr-review-mrx3xwms/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/okf-adr-review' && cp -R '.skill-downloads/adr-review-mrx3xwms' '.cursor/skills/okf-adr-review'

Codex
test -f '.skill-downloads/adr-review-mrx3xwms/SKILL.md' && test -s '.skill-downloads/adr-review-mrx3xwms/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/okf-adr-review' && cp -R '.skill-downloads/adr-review-mrx3xwms' '.agents/skills/okf-adr-review'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/adr-review-mrx3xwms'

openskills read 'adr-review-mrx3xwms'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/adr-review-mrx3xwms/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544
Skills Guide Bot

Create Architecture Decision Record

Documentation

Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.

Claude CodeintermediateSafe 69,659
Skills Guide Bot

Plan update with deep research

Documentation

Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.

Claude CodeadvancedSafe 248,015
Skills Guide Bot