ca-audit
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
npx skills add arbiterForge/codeArbiter --skill ca-audit --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-audit — promotion packet Everything codeArbiter logs, it logs append-only and scattered: `overrides.log`, `triage.log`, `decisions/`, `sprint-log.md`, `checkpoints/`. This command assembles them into the one document a team lead, compliance reviewer, or auditor actually asks for: *what happened in this window, who authorized it, and what is still open.* Read-only over every source; its only write is the packet. ## Window - `<from-ref> <to-ref>` — two tags/SHAs (e.g. `v1.2.0 v1.3.0`). - `--since-checkpoint` — from the `last-checkpoint` record to HEAD. - `--since <date>` — ISO date to HEAD. - No argument → from the most recent tag to HEAD (no tags → last checkpoint; neither → BLOCK and ask for an explicit window). ## Flow 1. Resolve the window to a commit range and a time range; both appear in the packet header. 2. Gather, citing each source file: - **Commits** — `git log` over the range, grouped by Conventional-Commit type; merge commits listed with their PR reference. - **Overrides** — every `overrides.log` line in the time range, verbatim (including `SECURITY-OVERRIDE` and `DEV:` entries), each with its `BY:` identity. - **Triage** — every small-lane classification in `triag
- Window
- Flow
- Hard gate
- When NOT to use
What does the ca-audit skill do?
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.