final-audit

Run a cross-cutting code review by reading the parent PRD, all child issues, and every modified file to detect integration faults. The audit compiles all in-scope files, builds a mental model of module interactions, and checks for systemic bugs before release.

A cross-cutting audit is a holistic review of a feature's entire codebase to identify systemic bugs, security vulnerabilities, and consistency errors. You need it before release to catch cross-module integration faults that individual PR reviews miss.

Generate a prioritized audit report by scanning all feature files and grouping findings by severity. The report categorizes issues into Security, Logic, Consistency, and Best practices, detailing precise file locations and suggested fixes, then saves to a user-specified location.

Yes, you can detect security vulnerabilities and race conditions across modules by reading every in-scope file. The audit checks for cross-cutting consistency issues, security gaps, logic errors, and duplicated logic to ensure feature-wide release readiness.

Yes, the final audit works on features across multiple repositories by discovering the parent PRD and compiling all created or modified files. It reads every file in scope to perform a holistic review and catch integration problems.

The best way to find systemic bugs is running a cross-cutting audit that reads every file in scope. This holistic review builds a mental model of interfaces and interactions, uncovering consistency errors and logic faults hidden in individual PRs.