health-audit

A repository health audit scans project structure, recent diffs, core docs, CI status, and testing to surface critical, security, and sustainability findings. It produces a permanent audit log under docs/audits/ with severity, impact, and traceable findings.

You convert codebase audit findings into actionable engineering tasks by generating consolidated health-sprint prompts stored in prompts/. These prompts include objectives, file manifests, specific file paths, commands, and binary success criteria.

Run a repository health check during onboarding to a new repo baseline, scheduled monthly maintenance for production services, pre-release risk assessment, or triage before architecture changes to identify critical build and sustainability problems.

Automated security audits require read and write access to repository files, the ability to create docs/audits/ and prompts/ entries, and generation of file manifests with binary success criteria.

The best way to assess pre-release risk is to run a health audit that scans CI status and testing to surface critical findings, then converts those findings into executable engineering commissions with binary success criteria.