adr-audit

Lints the Architecture Decision Record corpus for broken references, numbering issues, and invalid statuses.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill adr-audit-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-audit
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/adr-audit
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill adr-audit-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architecture Decision Records drift out of sync as a project grows: numbers get duplicated, supersede links break, template placeholders survive into ratified records, and the index goes stale. This Skill runs a read-only, corpus-wide consistency lint so you can find and fix those problems before a release. ## Core Features & Use Cases - Corpus-wide lint: Detects malformed files, invalid statuses, duplicate numbers, dangling ADR references, broken supersede pairs, placeholder residue, numbering holes, and stale indexes via the adr MCP tool's audit action. - Severity-ranked findings with remediation: Errors and warnings are grouped by class, each paired with concrete fix guidance and pointers to follow-up commands like /marvin:adr-review and /marvin:adr-supersede. - Read-only by design: The audit changes nothing; the single exception is regenerating the index, and only after explicit user confirmation. - Use Case: Before cutting a release, ask for an ADR health check to confirm no record cites a nonexistent ADR, no two files share a number, and every superseded decision links to its successor. ## Quick Start Ask the assistant to audit the ADRs and report any consistency errors in the decision record corpus.

Frequently Asked Questions about adr-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Architecture Decision Records for consistency errors?▼

Run the adr-audit skill, which calls the adr MCP tool's audit action to lint every record in the corpus. It reports typed findings with severities, errors first, each paired with remediation guidance.

What problems does an ADR lint detect?▼

The audit detects malformed files, invalid statuses, duplicate numbers, dangling ADR references, broken supersede pairs, leftover template placeholders, numbering holes, and a stale or missing corpus index.

Does the ADR audit modify my decision records?▼

No, the audit is read-only and never edits a record. The single exception is regenerating the corpus index via the adr tool's index action, and only after you explicitly confirm.

What is the difference between an ADR audit and an ADR review?▼

The audit checks corpus-wide structural consistency such as numbering, references, and statuses. A review evaluates the quality of a single decision's content, which is handled by the separate adr-review command.

Why does the ADR audit report numbering holes as warnings?▼

Numbering gaps are usually harmless history, such as withdrawn drafts, so they are warnings rather than errors. The guidance is to document them if the team cares, and never renumber existing records to close gaps.