adr-review
Evaluates the quality and reasoning of written ADRs via targeted feedback.
Install
mkdir -p .claude/skills/adr-review-ahamedzoha && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18140" && unzip -o skill.zip -d .claude/skills/adr-review-ahamedzoha && rm skill.zipInstalls to .claude/skills/adr-review-ahamedzoha
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Review an ADR the user has written in docs/adr/. Use when the user says an ADR is ready for review or asks for feedback on a decision record. Never use this to write or rewrite an ADR for them.Key capabilities
- →Review problem framing in an ADR
- →Check for option fairness
- →Evaluate trade-offs and consequences
- →Assess reversibility and revisit triggers
- →Identify weak reasoning in an ADR
- →Suggest updates to the index in `docs/adr/README.md`
How it works
The skill reviews an ADR for problem framing, option fairness, trade-offs, consequences, reversibility, revisit triggers, and weak reasoning. It delivers feedback as questions and suggestions.
Inputs & outputs
When to use adr-review
- →Review architecture decisions
- →Check ADR completeness
- →Verify decision logic
About this skill
Run the workflow in docs/playbooks/adr-review.md.
You review only — you never write the ADR. Check problem framing, option
fairness, trade-offs and consequences, reversibility, the revisit trigger, and
any weak reasoning. Deliver feedback as pointed questions and concrete
suggestions; let the user write the words. If it supersedes an earlier ADR,
confirm the index in docs/adr/README.md is updated.
When not to use it
- →When the user wants to write an ADR
- →When the user wants to rewrite an ADR
Limitations
- →The skill reviews only
- →The skill never writes the ADR
How it compares
This skill provides structured feedback on an ADR, guiding the user to improve the document rather than directly editing it.
Compared to similar skills
adr-review side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| adr-review (this skill) | 0 | 1mo | No flags | Beginner |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| python-code-style | 9 | 5mo | Review | Intermediate |
| code-review-excellence | 19 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
python-code-style
wshobson
Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.
code-review-excellence
wshobson
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
code-walk-thru
pchalasani
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
schema-markup
davila7
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.