Skip to content

tvproductions/gzkit / .agents/skills/gz-adr-audit

gz-adr-audit

Verified

Use for an ADR's Gate-5 audit; provides the audit templates and procedure.

FileKindSize
SKILL.mdskill md18.2 KB
assets/AUDIT.template.mdmarkdown2.1 KB
assets/AUDIT_PLAN.template.mdmarkdown2.1 KB

assets/AUDIT_PLAN.template.md

View on GitHub
# AUDIT PLAN TEMPLATE (Gate-5) — Replace Placeholders

| Field | Value |
| ----- | ----- |
| ADR ID | {{ADR_ID}} |
| ADR Title | {{ADR_TITLE}} |
| SemVer | {{SEMVER}} |
| ADR Dir | {{ADR_DIR}} |
| Audit Date | {{AUDIT_DATE}} |
| Auditor(s) | {{AUDITORS}} |

## Purpose

Confirm {{ADR_ID}} implementation is complete by validating its claims with reproducible CLI evidence.

**Audit Trigger:** (e.g., post-implementation stability check, pre-release confirmation, Gate-5 validation)

## Scope & Inputs

**Primary contract surfaces:**

List the specific CLI commands, reporter surfaces, or behaviors that this ADR introduces or modifies.

Example (adapt to ADR):

- `uv run gz <verb> <target> ...`
- Config sources: `.gzkit/manifest.json`
- Registry/manifest: `.gzkit/manifest.json`, `.gzkit/ledger.jsonl`

**System health surfaces (use when relevant):**

- `uv run gz status --table`
- `uv run gz state --json`
- `uv run gz validate --documents`
- `uv run gz check`

## Planned Checks

| Check | Command / Method | Expected Signal | Status (Planned) |
|-------|------------------|-----------------|------------------|
| (ADR-specific check 1) | (command) | (expected outcome) | Pending |
| (ADR-specific check 2) | (command) | (expected outcome) | Pending |
| Docs build (if docs changed) | `uv run mkdocs build --strict` | Build clean | Pending |
| Document validation (if docs changed) | `uv run gz validate --documents` | Zero violations | Pending |
| (Add more checks as needed) | | | Pending |

## Risk Focus

Highlight higher-risk seams (e.g., new flags, calendar normalization, receipt immutability).

## Findings Placeholder

Will be captured in `AUDIT.md` — do not populate here beyond structural notes.

## Acceptance Criteria

- All Planned Checks executed; results recorded in `audit/AUDIT.md` with ✓/✗/⚠.
- Proof logs saved under `{{ADR_DIR}}/audit/proofs/` and referenced in `audit/AUDIT.md` (co-located, committed).
- ADR present in index/status with correct state; backlinks maintained when applicable.
- No edits to accepted ADR prose; hygiene via follow-up ADR if required.

## Attestation Placeholder

Human will complete in `AUDIT.md` with final ✓ summary.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall