ca-audit
SolidAssemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
Install
Quality Score: 81/100
Skill Content
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
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.
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.
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.