← ClaudeAtlas

codebase-auditlisted

Use when running a comprehensive codebase verification. Dispatches parallel agents across disjoint scopes to check invariant compliance, dead code, test coverage gaps, and naming consistency.
LucaDominici/arbiter · ★ 0 · AI & Automation · score 70
Install: claude install-skill LucaDominici/arbiter
# Codebase Audit **Purpose:** Systematic whole-codebase verification using parallel read-only agents. ## When to Use - Before a major release - After a large refactor - Periodic health checks - Onboarding to an unfamiliar codebase ## Audit Scopes Divide the codebase into disjoint scopes and delegate each to a `codebase-scanner` agent: | Scope | What to Check | |-------|--------------| | **Dead code** | Unused exports, unreachable functions, commented-out blocks | | **Naming consistency** | Conventions followed (camelCase, snake_case per layer) | | **Test coverage gaps** | Source files without a corresponding test file | | **Error handling** | Unchecked errors, swallowed exceptions, missing fallbacks | ## Execution For each scope, delegate to `codebase-scanner`: ``` Delegate to codebase-scanner: "Find all <scope> issues in src/" ``` Run scopes in parallel when possible. ## Output Format ```markdown ## Codebase Audit Report **Date:** <date> **Scope:** Full / Partial (<modules>) ### Dead Code - <file:line — description> ### Naming Inconsistencies - <file:line — convention violated> ### Test Coverage Gaps - <source file without test> ### Error Handling Gaps - <file:line — description> ### Summary - Total issues found: <N> - Critical: <N> - Recommended actions: <list> ``` ## Constraints - Read-only. No edits during audit. - Do not fix issues inline — create task briefs for fixes.