audit-workflow

To run a comprehensive project health audit, initiate the workflow to orchestrate sequential multi-agent analyses across architecture, security, and code quality. It aggregates findings into a health score and generates a consolidated markdown report for your project.

Yes, you can scope code review and security audits to full projects, selected directories, single files, or commit ranges. Change-based audits use git diffs or --since ranges to isolate recent modifications for targeted health checks.

The best way to automate pre-release code checks is using a scope-aware audit workflow that runs sequential senior-reviewer and security-auditor agents. This avoids duplicate findings and generates a consolidated health score before release.

The health score calculation works by sequentially running architecture, security, and code quality analyses, then aggregating the severity of all confirmed findings into a single quantitative metric within a consolidated markdown audit report.

Yes, the audit workflow supports optional remediation routing for confirmed critical findings. It categorizes issues into structural refactoring or behavioral security flows, complete with verification steps and test cycles.

You should use an end-to-end project audit instead of a standard code review when you need onboarding assessments, periodic health checks, or pre-release validation that combines architecture, security, and code quality into a unified health score.