adr-review
Review code changes against accepted ADRs for compliance violations
Profile →npx skills add ruvnet/ruflo --skill adr-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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__plugin_ruflo-core_ruflo__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 th
- When to use
- Steps
What does the adr-review skill do?
Review code changes against accepted ADRs for compliance violations
How do I install it?
Run `npx skills add ruvnet/ruflo --skill adr-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.