메뉴
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".
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Mattilsynet/gh-report --skill adr-lint명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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".
SKILL.md 표시 중
SOC 직업 분류 기준
| 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.