Adr Verify
- 593 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
adr-verify is a Claude Code skill that reads adr-patterns and adr-edges namespaces to surface dangling references, supersede cycles, and status mismatches in Architecture Decision Record graphs for developers who need va
About
adr-verify is a ruflo companion skill to adr-index that audits persisted ADR graphs via claude-flow memory tools and Bash, exiting with code 1 when cycles are detected. It flags dangling edges pointing at missing ADR IDs—often from sibling repos or deletions—supersede cycles such as ADR-A supersedes ADR-B while ADR-B supersedes ADR-A, and status mismatches when an ADR is marked superseded inconsistently. Developers run it after ADR imports to catch data corruption before agents or teams rely on the graph. Allowed tools include Bash plus mcp__claude-flow__memory_list and memory_retrieve.
- adr-verify
Adr Verify by the numbers
- 593 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #676 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill adr-verifyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 593 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you verify ADR graph integrity after import?
Use adr-verify for development tasks
Who is it for?
Teams persisting Architecture Decision Records in claude-flow memory who need automated graph validation after imports or merges.
Skip if: Projects without an adr-index import or persisted adr-patterns and adr-edges namespaces to validate.
When should I use this skill?
User imports ADRs or asks to verify dangling references, supersede cycles, or ADR status consistency.
What you get
Integrity report listing dangling refs, supersede cycles, status mismatches, and non-zero exit on cycles
- Integrity issue report
- Non-zero exit on cycles
Files
ADR Verify
Companion to adr-index. After import, reads the persisted graph and surfaces integrity issues:
- Dangling refs — edge points at an ADR ID that doesn't exist in
adr-patterns. Common cause: the referenced ADR is in a sibling repo or got deleted. - Supersede cycles —
ADR-A supersedes ADR-BandADR-B supersedes ADR-A(or longer cycles). Always data corruption. - Status mismatches — an ADR is the source of a
supersedesedge but its own status isn'tSuperseded. Usually a missed status update during a successor ADR's promotion.
When to use
- Right after
adr-indexto confirm the graph is healthy - In CI as a fail-closed gate (
VERIFY_STRICT=1exits 1 on any issue) - Before publishing an ADR-related release
Steps
node plugins/ruflo-adr/scripts/verify.mjsOptional env:
VERIFY_FORMAT=json— JSON instead of markdownVERIFY_STRICT=1— exit 1 on ANY issue (default: only on cycles)
Exit codes
| Code | Meaning |
|---|---|
0 | Graph healthy (or dangling refs / status mismatches present in non-strict mode) |
1 | Supersede cycle detected, OR strict mode + any issue present |
Cross-references
adr-index— populates the data this skill verifiesscripts/import.mjs— has its own dry-run validation; this skill is the read-back companion
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kFAQ
What issues does adr-verify detect?
adr-verify surfaces dangling references to missing ADR IDs, supersede cycles in the adr-edges graph, and status mismatches between ADR records in adr-patterns and their edge relationships.
When does adr-verify exit with code 1?
adr-verify exits 1 when supersede cycles are found—such as mutual supersede links—because those patterns indicate corrupted Architecture Decision Record graph data.