mcpbeat

Ca Audit

arbiterforge/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.

700 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
138
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-audit

The instruction itself

5 sections, as written by the author

$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

  • Resolve the window to a commit range and a time range; both appear in the packet header.
  • Gather, citing each source file:
  • Commitsgit 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 triage.log in range.
  • Decisions — ADRs created or superseded in range (from decisions/ file dates and the

supersede chains), each with its Decided-by attribution.

  • Sprint auto-decisions — entries from sprint-log.md in range; list every low-confidence

entry verbatim, count the high ones.

  • Open questions — all currently-unresolved [CONFIRM-NN] items.
  • Checkpoint findings — from the most recent checkpoints/*.md: findings still open.
  • Write the packet to <project-root>/.codearbiter/audits/<YYYY-MM-DD>.md (second run the

same day appends -2, -3, … — an existing packet is never overwritten). Surface the path and

a three-line summary: commits, overrides, open items.

Hard gate

Read-only over every source — MUST NOT modify any log, decision, or checkpoint while assembling.

MUST NOT overwrite an existing packet. MUST quote override and low-confidence sprint entries

verbatim — never paraphrase an audit line. An empty section is stated as empty, never omitted —

"no overrides in window" is itself the finding.

When NOT to use

  • Live project state right now → $ca-status.
  • Triggering reviews → $ca-checkpoint (this command only reports what reviews already found).

How to use it

Copy the folder

Take arbiterforge/ca-audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.