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: 83/100
Skill Content
Details
- Author
- arbiterForge
- Repository
- arbiterForge/codeArbiter
- Created
- 4 months ago
- Last Updated
- today
- Language
- Python
- License
- AGPL-3.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
audit
Use when the user wants to assess the state of a feature, flow, or module — a UX, security, performance, or accessibility audit; cataloging bugs, gaps, and opportunities; retesting open findings; escalating a finding to the backlog; or updating audit methodology. Fires on "I want to do a UX / security / performance / accessibility audit", "before we ship I want to audit X", "audit the X flow or module", "catalog the state of X", "list bugs and gaps in X", "retest open findings", "register a finding under audit X", "escalate finding <id> to backlog", and /aidex:audit commands. Not for: auditing the Claude Code setup itself like skills or MEMORY.md (/aidex:aidex); creating plans (/aidex:plan) or decisions (/aidex:decision); generic backlog items not from a finding (/aidex:backlog).
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.