Skip to content
Back to skills

Adr Review

ASecurity

Review code changes against accepted ADRs for compliance violations

  • 73,733 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added May 27, 2026
data-aibashgit

Works with

  • mcp

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add ruvnet/ruflo --skill adr-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Adr Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Adr Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ruvnet-adr-review/badge)](https://www.skillsdirectory.com/skills/ruvnet-adr-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: adr-review
description: Review code changes against accepted ADRs for compliance violations
argument-hint: "[--branch BRANCH]"
allowed-tools: mcp__claude-flow__agentdb_hierarchical-query mcp__claude-flow__agentdb_causal-query mcp__claude-flow__memory_search Bash Read Grep Glob
---

# ADR Review

Review code changes against accepted Architecture Decision Records to detect violations, drift, and non-compliance.

## When to use

Before merging a PR, after significant code changes, or as part of a periodic compliance check. Use this to ensure code changes respect the architectural decisions the team has agreed upon.

## Steps

1. **Get diff** -- Run `git diff main...HEAD --name-only` (or the specified branch) to list changed files. Then run `git diff main...HEAD` to get the full diff content.

2. **Find relevant ADRs** -- For each changed file:
   - `Grep` the file for ADR references (`ADR-\d+`)
   - `Grep` `docs/adr/` for ADRs that mention the changed file paths or modules
   - Call `mcp__claude-flow__memory_search` with the file path and change summary to find semantically related ADRs

3. **Load ADR content** -- `Read` each relevant ADR file. Focus on:
   - The **Decision** section (what was decided)
   - The **Status** (only enforce "accepted" ADRs)
   - The **Consequences** (expected constraints)

4. **Check for violations** -- Analyze each changed file against its relevant ADRs:
   - Does the code change contradict an accepted decision?
   - Does it use a technology/pattern that an ADR explicitly rejected?
   - Does it modify a module in a way the ADR's consequences warned against?
   - Is the code referencing a deprecated or superseded ADR?

5. **Query relationship graph** -- Call `mcp__claude-flow__agentdb_causal-query` to check if any referenced ADRs have been superseded. If so, flag that the code references an outdated decision.

6. **Report** -- Present findings as a compliance report:
   ```
   ## ADR Compliance Report

   ### Violations
   - [ ] <file>:<line> — violates ADR-NNN: <reason>

   ### Warnings
   - [!] <file> references superseded ADR-NNN (replaced by ADR-MMM)

   ### Compliant
   - [x] <file> — consistent with ADR-NNN

   ### Unlinked Changes
   - [?] <file> — no ADR coverage (consider creating one)
   ```

7. **Suggest actions** -- For each violation, suggest whether to update the code or propose a new ADR to supersede the violated one.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…