cast-audit

You can automate a monthly codebase audit by dispatching four parallel researchers to analyze security, bugs, performance, and test coverage, compiling findings into a dated report at ~/.claude/reports/cast-audit-YYYY-MM-DD.md.

Running parallel codebase audits for bugs and test coverage is best handled by dispatching four modular researchers simultaneously, which generates individual section reports before compiling a final collated audit document.

Yes, monthly codebase audits support scheduled execution to automate recurring checks, dispatching parallel researchers on a set schedule to produce a dated audit report tracking drift and regressions over time.

The codebase audit report applies modular section audits, generating separate per-section reports for security, bugs, performance, and test coverage before collating them into the final dated markdown file.

The final collated codebase audit report is saved locally as a markdown file at ~/.claude/reports/cast-audit-YYYY-MM-DD.md, using the current date to maintain a chronological audit history.

Parallel codebase audits require scheduling and parallel dispatch capabilities to function, meaning the process depends on a supported environment to execute the four researchers and compile the final collated report successfully.