audit
/audit
Sprawdza, czy projekt trzyma kurs: lintuje decyzje i ocenia kod w jednym przebiegu, do audytu ADR, dryfu architektury i raportu governance, tylko do odczytu.
- Autor
- rvdbreemen ↗
- Repozytorium
- adr-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 24.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Sprawdza, czy projekt trzyma kurs: lintuje decyzje i ocenia kod w jednym przebiegu, do audytu ADR, dryfu architektury i raportu governance, tylko do odczytu.
Argumenty
/audit [--whole-codebase | a diff path; defaults to the working tree]
Oryginalny opis (EN)
Are we still on course? Lint the decisions and judge the code in one run. Use for ADR audit, architecture drift, a whole-codebase compliance check, or a governance report. Read-only.
Jak działa
- Why one command for two questions
- Run it
- Read the exit code before you read the output
- Responding to findings
- Which gates a green audit covers
- Where it fits
Podgląd SKILL.md
--- name: audit description: "Are we still on course? Lint the decisions and judge the code in one run. Use for ADR audit, architecture drift, a whole-codebase compliance check, or a governance report. Read-only." argument-hint: "[--whole-codebase | a diff path; defaults to the working tree]" allowed-tools: [Read, Bash, Glob, Grep] --- # ADR Audit Reply in the language the user writes in; default to English. Keep command output, identifiers, paths, and ADR file content unchanged. Use `$ARGUMENTS` to pick the scope. Empty means the whole codebase, because that is the question people mean when they ask whether the project is still on course. Read-only: this skill reports, it never edits an ADR or a source file. ## Why one command for two questions Two answers are needed and either one alone is misleading: - **Are the decisions any good?** A clean judge over vague ADRs proves nothing, because a vague rule cannot be violated. - **Does the code obey them?** A sharp ADR set nobody checks the code against is documentation, not governance. `bin/adr-audit` runs `adr-lint` and `adr-judge` together so the caller does not have to know the answers come from two binaries. ## Run it ```bash # The whole codebase: every tracked file judged as if newly added, so forbid # rules reach code no recent diff touched. "$ADR_KIT/bin/adr-audit" --whole-codebase --adr-dir docs/adr --repo-root . # A specific diff: the hook and pull-request case. git diff --unified=0 origin/main...HEAD | "$ADR_KIT/bin/adr-audit" --diff - # Machine-readable, for a CI job or another tool. "$ADR_KIT/bin/adr-audit" --whole-codebase --format json ``` Add `--llm` to include the judge's LLM pass for `llm_judge` ADRs. It costs money and time proportional to the number of opted-in ADRs, so confirm with the user before adding it — never on your own initiative. ## Read the exit code before you read the output The two failures have different owners, so they have different codes: | Exit | Meaning | Who fixes it | |---|---|---| | 0 | on course | nobody | | 1 | the code violates an Accepted ADR | the author of the code, or supersede the decision | | 3 | the ADR set fails its own gates | the author of the records | | 4 | both | both, and report them separately | | 2 | the audit could not run | tooling or configuration; it did **not** answer "no" | Never collapse 1 and 3 into "the audit failed". Say which one, and to whom it belongs. Exit 2 is not a finding: report that the audit could not run and why, and do not present its silence as a pass. ## Responding to findings - **Code violations** — cite ADR, file and line. Offer to fix the code, or, if the decision itself is what is wrong, to supersede it with `/adr-kit:adr`. Never work around an Accepted ADR silently. - **ADR-quality failures** — name the failing gate, not just the ADR. Offer `/adr-kit:grill ADR-NNN` for a Proposed record. An Accepted record's body is immutable: the honest routes are a supersession or a retirement, never a rewrite. - **Whole-codebase mode surfacing old violations** — expected and worth saying plainly. A rule added after a file was written has never been applied to that file. Offer a remediation task rather than a large unrequested edit. ## Which gates a green audit covers By default the lint half runs `completeness`, `audit` and `consistency` -- the structural gates, which have exact answers. **A green audit at the default set is not a statement that the records are sharp**, and this command's own rationale turns on that distinction: a clean judge over vague ADRs proves nothing, because vague rules cannot be violated. `--gates` passes a set through to `adr-lint`. `--gates all` adds `schema`, `evidence`, `clarity`, `policy` and `quality`. | Question | Gate set | |---|---| | Are the records structurally sound? | default | | Are they sharp enough to be violated? | `--gates all` | | Would they survive release? | `--strict` | Say which set produced the answer when you report it. "The audit is green" is a different claim depending on the set, and the reader cannot tell from the verdict line alone. ## Where it fits - `/adr-kit:judge` judges one staged diff at commit time. Narrower and faster. - `/adr-kit:lint` checks the records alone. - `/adr-kit:guardian` runs a version of this combination on a cadence. - `/adr-kit:audit` is the on-demand form a person, a hook or a CI job can simply demand, and the only one that reaches code no diff has touched. `bin/adr-discover` is a different thing despite the old name: it is the init scanner that looks for decision-shaped artefacts. It does not audit anything.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · rvdbreemen/adr-kit | 100 | MIT |
| marcel-bich/marcel-bich-claude-marketplace | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| userKael/rastro | 100 | MIT |
| Archont561/qgis-agent-harness | 100 | MIT |
| lilly-logic-labs/lll-skills | 100 | MIT |
| Come-In-Labs/agent-skills | 100 | MIT |
| minanyang/10x-agent | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 61410d49b5b8 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100docs-governance
Kieruje szerokie prośby o zarządzanie dokumentacją do istniejących skilli ECC i uruchamia opcjonalny audyt tylko do odczytu ról dokumentów, linków, indeksów ADR i odwołań do dowodów. - 100architecture-review
Ocenia decyzje architektoniczne, zgodność z ADR i sprzężenie przy zmianach projektowych oraz przed scaleniem zmian. - 100adr
Dokumentuje decyzje architektoniczne z automatyczną numeracją według wzorca ADR. - 100architecture
Wspiera projektowanie systemu, tworzenie ADR i przegląd architektury przy decyzjach architektonicznych. - 100adr-compliance
Pomaga audytować zgodność kodu z zaakceptowanymi rekordami decyzji architektonicznych (ADR): sprawdzanie kodu względem ADR, wykrywanie naruszeń i egzekwowanie decyzji. - 100judge
Ocenia staged diff względem zaakceptowanych ADR, przy zgodności z ADR, zablokowanym pre-commit i naruszeniach architektury.