adr-verify
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
Profile →npx skills add ruvnet/ruflo --skill adr-verify --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 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` — e
- When to use
- Steps
- Exit codes
- Cross-references
node plugins/ruflo-adr/scripts/verify.mjs
What does the adr-verify skill do?
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
How do I install it?
Run `npx skills add ruvnet/ruflo --skill adr-verify --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.