メニュー
Run `adr-fmt --lint` against the ADR corpus and triage diagnostics by namespace (T0xx template, L0xx links, S0xx supersedes/lifecycle, P0xx parser). Use when the user asks to lint ADRs, check ADR integrity, validate the corpus, or mentions "adr-fmt --lint".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Surface the architectural rules applicable to a specific crate via `adr-fmt --context <CRATE>`. Use when an agent (especially oracle, moltke, hopper) needs the binding constraints for code in a crate before deciding or editing, or when the user asks "what rules apply to crate X?"
List inbound References and Supersedes citations of a target ADR via `adr-fmt --refs <ADR_ID>`. Use when the user asks who references / supersedes / cites an ADR, wants to assess blast radius before changing an ADR, or mentions "adr-fmt --refs".
Print the ADR domain tree (parent → child via AFM-0020 parent-edge model) optionally filtered by domain prefix, via `adr-fmt --tree [DOMAIN]`. Use when the user wants to enumerate ADRs in a domain, see the architectural hierarchy, or mentions "adr-fmt --tree".
| name | adr-lint |
| description | Run `adr-fmt --lint` against the ADR corpus and triage diagnostics by namespace (T0xx template, L0xx links, S0xx supersedes/lifecycle, P0xx parser). Use when the user asks to lint ADRs, check ADR integrity, validate the corpus, or mentions "adr-fmt --lint". |
Wrapper skill around adr-fmt --lint. Read-only against the corpus
(AFM-0001). Advisory exit semantics: warnings ≠ failure (AFM-0003).
Build is cheap and dogfoods the latest source. Prefer the freshly-built
binary over a stale target/release/adr-fmt:
cargo run -p adr-fmt --release -- --lint
Capture both stdout and the exit code. Do not collapse them.
| Exit | Meaning | Action |
|---|---|---|
0 | Analysis complete (warnings allowed) | Triage, do not "fail" the run |
1 | Infra error or structural error | Halt; report verbatim |
Never edit the corpus to silence a warning unless the user explicitly asks for the fix. Warnings are signal for humans, not errors to suppress.
| Prefix | Source | Typical content |
|---|---|---|
T0xx | rules/template.rs | Per-file MADR template conformance |
L0xx | rules/links.rs | Cross-file link integrity |
S0xx | rules/links.rs | Lifecycle / Supersedes consistency |
P0xx | parser.rs (AFM-0017) | Parser-stage structural diagnostics |
When reporting back to the user, group findings by prefix and cite the ADR ID + file:line as printed by adr-fmt. Do not paraphrase the diagnostic message — quote it.
Terse, parseable. Skip prose.
Lint: <PASS_CLEAN | PASS_WITH_WARNINGS | FAIL>
Exit: <n>
ADRs scanned: <n>
Diagnostics: T=<n> L=<n> S=<n> P=<n> other=<n>
Top findings:
- <code> <ADR-ID> <file>:<line> <message>
- ...
Notes: <abnormal stderr lines, if any>
PASS_CLEAN only when diagnostic count is 0. Any warnings → PASS_WITH_WARNINGS.
FAIL only on exit ≠ 0.
--lint is in scope here.adr-fmt.toml (AFM-0001); there is no
--corpus override.