ca-audit

Solid

Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.

AI & Automation 144 stars 7 forks Updated yesterday AGPL-3.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
72
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# $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 ...

Details

Author
arbiterForge
Repository
arbiterForge/codeArbiter
Created
4 months ago
Last Updated
yesterday
Language
Python
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

sdlc-audit

The periodic whole-repo audit — measure the codebase as it now stands, then judge it against four lenses (conformance to its own rules, structural erosion, measured debt, fitness for purpose). Triggers on "audit", "tech debt", "architecture review", "whole repo", "code health", "what has rotted". Read-only by default; files tracked issues only when asked. Use when the user runs /sdlc-audit, or when /sdlc-status reports an audit is due.

6 Updated 4 weeks ago
swapnil-agrim
Data & Documents Listed

audit

Audit a documentation-led repo against its own conventions — contiguous ADR numbering, INDEX sync, plan/ coverage, required sections, status validity, cross-reference resolution, language mandate, ADR-privacy leaks into user-visible code, cross-worktree collisions (duplicate numbers, duplicate plan ownership, same ADR edited on two branches), and — for a multi-repo product — cross-repo federation checks (bidirectional membership, identity collisions, dangling cross-repo references, roll-up drift, convention drift). Reports a punch list and offers to fix the mechanical issues. Use when the user says "audit the ADRs", "lint the conventions", "check repo consistency", "are the ADRs in sync", or invokes /audit.

12 Updated 4 days ago
EvolveHQ
Code & Development Listed

audit

Audit a whole project directly in-session with a small dispatched crew, in one of two modes — assess produces an evidence-cited health report across documentation, architecture, code quality, testing/reliability, security/config, and product readiness; purge removes what is proven dead or false (stale code, untrue docs, stale branches, unused dependencies) behind a human approval gate. Use when preparing for a release or external review, assessing overall project health, or purging dead code, doc drift, and stale branches. Not for a single diff or PR — use the native /code-review and /security-review, or `validate` to orchestrate them on one branch.

0 Updated today
jwogrady