Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / Unknown statuses; exit 1 on cycles
Review the instructions the agent will receive before you install.
Companion to adr-index. After import, reads the persisted graph and surfaces integrity issues:
adr-patterns. Common cause: the referenced ADR is in a sibling repo or got deleted.ADR-A supersedes ADR-B and ADR-B supersedes ADR-A (or longer cycles). Always data corruption.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.
adr-index to confirm the graph is healthyVERIFY_STRICT=1 exits 1 on any issue)node plugins/ruflo-adr/scripts/verify.mjs
Optional env:
VERIFY_FORMAT=json — JSON instead of markdownVERIFY_STRICT=1 — exit 1 on ANY issue (default: only on cycles)| 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 |
adr-index — populates the data this skill verifiesscripts/import.mjs — has its own dry-run validation; this skill is the read-back companionadr-reindex — reconciles a deleted ADR that adr-verify cannot detectNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Coordinate multiple AI agents by adjusting their communication structure and task assignments as workloads change. The skill describes performance monitoring, switching coordination patterns, forecasting agent capacity, and validating changes with rollback when performance worsens.