Skip to content
Back to skills

Gz Arb

ASecurity

Use to wrap QA commands in ARB receipts for attestation evidence or to audit lint patterns from receipts.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
businessgobashrailsdebugginggit

Works with

  • cli

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add tvproductions/gzkit --skill gz-arb --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gz Arb?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gz Arb
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tvproductions-gz-arb/badge)](https://www.skillsdirectory.com/skills/tvproductions-gz-arb)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: gz-arb
persona: main-session
description: Use to wrap QA commands in ARB receipts for attestation evidence or to audit lint patterns from receipts.
category: agent-operations
lifecycle_state: active
owner: gzkit-governance
last_reviewed: 2026-10-17
model: haiku
gz_command: arb advise
metadata:
  skill-version: "1.4.1"
revived_on: "2026-04-14"
revived_under: OBPI-0.25.0-33
revival_note: "ARB surface absorbed from airlineops/opsdev/arb under OBPI-0.25.0-33. The earlier retirement (2026-04-03, 'consolidated into gz-check') was itself drift — gz check never implemented ARB receipt emission, so the rule contract in .gzkit/rules/arb.md was referencing a nonexistent surface. Revival restores parity with the rule."
---

# gz arb

## Overview

Agent Self-Reporting middleware: wrap QA commands (ruff, ty, unittest, coverage) and emit schema-validated JSON receipts to `artifacts/receipts/`. These receipts are the canonical attestation evidence cited in Heavy-lane OBPI closeout claims per `AGENTS.md` § Attestation.

## When to Use

- Producing Heavy-lane attestation evidence (receipt IDs for lint, typecheck, tests, coverage)
- Debugging a failing QA step and needing a deterministic receipt artifact
- Summarizing recurring advice from recent lint runs to tune agent guardrails
- Auditing QA compliance across an ADR or release cycle

## Workflow

1. **Wrap the QA step via ARB** — pick the appropriate verb. For any claim
   category in the canonical list below (the list's home since 2026-09-17),
   use the canonical invocation from that table; those commands are locked
   by `CANONICAL_STEP_COMMANDS` and divergence is flagged by
   `gz arb validate` as non-canonical provenance (GHI #199).
   - `uv run gz arb ruff <paths>` — ruff lint (canonical for lint claims)
   - `uv run gz arb typecheck` — wraps `ty check . --exclude features/**`,
     the same target as `gz typecheck` and `gz closeout` (canonical for
     type-check claims). Do not restate the scope from memory: the verb
     and the gate both READ `CANONICAL_STEP_COMMANDS["typecheck"]`, so
     the table is the answer whenever this line disagrees with it.
   - `uv run gz arb step --name unittest -- uv run unittest-parallel -t . -s tests --buffer` —
     canonical for tests-pass claims
   - `uv run gz arb coverage` —
     canonical for coverage-floor claims
   - `uv run gz arb step --name mkdocs -- uv run mkdocs build --strict` —
     canonical for docs-build-clean claims

   The canonical invocations apply to `uv run gz obpi complete`,
   `uv run gz adr emit-receipt`, any `gz` CLI attestation string, and
   `git commit -m` messages. Worked example of an enriched attestation:
   `docs/governance/agent-contract-rationale.md#attestation--worked-example`.
   - `uv run gz arb step --name <name> -- <command>` — any step not named
     in the canonical table (diagnostic or bespoke QA only; not valid
     attestation provenance)
   - `uv run gz arb ty` — raw `uvx ty check` passthrough; **not** an alias
     of `gz arb typecheck` (which wraps the canonical scope with the ARB
     schema).
     Use `gz arb ty` when you need the raw `ty` output without ARB receipt
     emission, or to pass custom `ty` flags directly.
2. **Validate the emitted receipts** — `uv run gz arb validate --limit 20`
3. **Summarize recent receipts** — `uv run gz arb advise --limit 20`
4. **Extract recurring patterns** (optional) — `uv run gz arb patterns`
5. **Cite receipt IDs in the attestation** per `AGENTS.md` § Attestation
6. **Bound the store** (periodic, after harvesting) — `uv run gz arb archive --older-than 30d --dry-run`,
   then without `--dry-run` to relocate. Move-not-delete: aged receipts go to
   `artifacts/receipts/archive/`, and a receipt whose id is cited in the ledger is
   never moved, because a citation must keep resolving. Run it AFTER steps 3–4, so
   the harvest verbs have already read what they were going to read. There is no
   `purge` verb by design (GHI #594).

## Example

```bash
# Produce full attestation evidence for Heavy-lane closeout.
# Each invocation below is the canonical form. This skill is the home of the
# list since 2026-09-17; AGENTS.md § Attestation points here. Receipt name
# prefixes: arb-ruff-, arb-step-typecheck-, arb-step-unittest-,
# arb-step-coverage-, arb-step-mkdocs-.
uv run gz arb ruff src tests
uv run gz arb typecheck
uv run gz arb step --name unittest -- uv run unittest-parallel -t . -s tests --buffer
uv run gz arb coverage
uv run gz arb step --name mkdocs -- uv run mkdocs build --strict
uv run gz arb validate --limit 10
uv run gz arb advise --limit 10
```

## Output Contract

- `gz arb ruff` / `step` / `ty` / `coverage` — exit 0 on success, 1 on command failure, 2 on ARB internal error; receipt always emitted to `artifacts/receipts/<run_id>.json`
- `gz arb validate` — human text by default; `--json` for machine-readable
- `gz arb advise` — human text; `--json` for machine-readable
- `gz arb patterns` — Markdown report by default; `--compact` for one-liner; `--json` for machine-readable
- `gz arb archive` — human summary of the plan/result buckets; `--json` for machine-readable; `--dry-run` classifies without moving

## Validation

- Confirm receipts appear under `artifacts/receipts/` after each wrapped run.
- Run `uv run gz arb validate` and confirm `invalid=0` before citing receipt IDs in attestations.

## References

- Binding rule: `AGENTS.md` § Attestation (em-dash pattern + canonical invocations + lane behavior + receipt-ID discipline)
- Deep-dive: `docs/governance/arb-middleware.md` (core concept, command surface, receipt schema, exit codes, rationale)
- Command docs: `docs/user/manpages/arb.md`
- Manpage: `docs/user/manpages/arb.md`
- Absorption record: OBPI-0.25.0-33 under ADR-0.25.0

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.