How do I install the Adr Verify skill?

Run npx skillmds@latest add ruvnet/adr-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Adr Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Adr Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Adr Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Adr Verify?

ruvnet (@ruvnet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Adr Verify by ruvnet — Agent Skill

Name: Adr Verify
Rating: 4.2 (5 reviews)
Author: ruvnet

File contents

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-B and ADR-B supersedes ADR-A (or longer cycles). Always data corruption.
Status mismatches — an ADR is the source of a supersedes edge but its own status isn't Superseded. Usually a missed status update during a successor ADR's promotion.

What this skill cannot catch: an adr-patterns row for an ADR that was deleted from disk and has zero edges referencing it or from it — invisible to every check above (issue #2666). If the reported ADR count looks higher than what's actually on disk, run adr-reindex, not adr-verify again.

When to use

Right after adr-index to confirm the graph is healthy
In CI as a fail-closed gate (VERIFY_STRICT=1 exits 1 on any issue)
Before publishing an ADR-related release

Steps

node plugins/ruflo-adr/scripts/verify.mjs

Optional env:

VERIFY_FORMAT=json — JSON instead of markdown
VERIFY_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 verifies
scripts/import.mjs — has its own dry-run validation; this skill is the read-back companion
adr-reindex — reconciles a deleted ADR that adr-verify cannot detect

Source: ruvnet/ruflo → plugins/ruflo-adr/skills/adr-verify/SKILL.md

---name: adr-verifydescription: Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles--- # 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-B` and `ADR-B supersedes ADR-A` (or longer cycles). Always data corruption. - **Status mismatches** — an ADR is the source of a `supersedes` edge but its own status isn't `Superseded`. Usually a missed status update during a successor ADR's promotion. **What this skill cannot catch:** an `adr-patterns` row for an ADR that was deleted from disk and has zero edges referencing it or from it — invisible to every check above (issue #2666). If the reported ADR count looks higher than what's actually on disk, run `adr-reindex`, not `adr-verify` again. ## When to use - Right after `adr-index` to confirm the graph is healthy - In CI as a fail-closed gate (`VERIFY_STRICT=1` exits 1 on any issue) - Before publishing an ADR-related release ## Steps ```bash node plugins/ruflo-adr/scripts/verify.mjs ``` Optional env: - `VERIFY_FORMAT=json` — JSON instead of markdown - `VERIFY_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 verifies - `scripts/import.mjs` — has its own dry-run validation; this skill is the read-back companion - `adr-reindex` — reconciles a deleted ADR that `adr-verify` cannot detect --- **Source:** [`ruvnet/ruflo`](https://github.com/ruvnet/ruflo) → `plugins/ruflo-adr/skills/adr-verify/SKILL.md`

Frequently asked questions

Adr Verify