Adr Review

Runs a compliance check between your code changes and accepted Architecture Decision Records. Point it at a branch and it diffs the changes, searches for relevant ADRs in your docs folder, then flags violations where code contradicts what your team agreed to. It checks ADR status so you're not enforcing superseded decisions, catches references to outdated ADRs, and highlights files with no ADR coverage. The output is a simple checklist of violations, warnings, and compliant changes. Honest take: this only works if your team actually maintains ADRs, but if you do, catching architectural drift before merge is way better than during a postmortem six months later.

skills.sh installs: 745
GitHub stars: 81.4K
last updated: Aug 21, 2026

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

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

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.
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__plugin_ruflo-core_ruflo__memory_search with the file path and change summary to find semantically related ADRs
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)