How do I install the Ca Audit skill?

Run npx skillmds add majiayu000/ca-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ca Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ca Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ca Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ca Audit?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ca Audit by majiayu000 — Agent Skill

Name: Ca Audit
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

/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:
- 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 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).

---name: ca-auditdescription: Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.--- # /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 `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. 3. 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).

Frequently asked questions