caudit

Audit codebases for systemic quality issues with structured convergence workflows.

65|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/joshft/correctless --skill caudit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caudit
Source: https://github.com/joshft/correctless/tree/main/correctless/skills/caudit
Command: npx skills add https://github.com/joshft/correctless --skill caudit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-codebase software projects often accumulate systemic bugs and misalignment between teams. caudit provides a structured, Olympics-style audit workflow to surface, triage, and fix regressions across multiple agents.

Core Features & Use Cases

  • Coordination of multi-agent audits (spec, review, test, QA, verification) to surface systemic issues.
  • Post-feature, end-of-week, and pre-release checks scoped to changed files and dependencies.
  • Forensic logging and strict fix verification to prevent regressions and ensure traceability from finding to fix.

Quick Start

Launch the audit workflow with a preset (qa, hacker, perf) and a scope (changed or all) to begin converging on issues.

Frequently Asked Questions about caudit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a cross-codebase audit to catch regressions before merging?▼

Run a cross-codebase audit by launching a structured workflow with a preset like qa, hacker, or perf, scoped to changed files and dependencies to surface and triage high-priority findings pre-merge.

What is convergence-based code review and how does it catch systemic bugs?▼

Convergence-based code review coordinates multi-agent audits across spec, test, and QA roles to identify systemic quality issues, enforcing intensity gates and multi-round triage to catch codebase bugs.

When should I perform pre-release code quality checks on changed files?▼

Perform pre-release code quality checks post-feature release, end-of-week, or pre-merge to surface regressions. Scope checks to changed files and dependencies to ensure issues are remediated before merging.

Can I verify that bug fixes pass an intensity gate without causing new regressions?▼

Yes, the audit workflow enforces mandatory fix verification and forensic logging to prevent regressions, ensuring traceability from finding to fix pre-merge.

What's the best way to triage code quality issues across multiple agents?▼

Triage code quality issues across multiple agents using a structured Olympics-style audit workflow that applies multi-round triage, forensic logging, and strict fix verification to remediate findings.