audit

To automate post-build code review, provide a CR-ID to trigger the review gate. The system locates relevant specs, runs gate checks across three mandatory perspectives, and produces a PASS or BLOCKED verdict to validate the implementation before closure.

A post-build review gate validates a finished implementation before closure. You need it after implementation-build has completed to evaluate the CR across Critical, High, and Normal severity perspectives, ensuring code quality before finalizing.

To validate a completed CR build before closure, run the post-build review gate using the CR-ID. It runs Critical and High severity checks in parallel for maximum rigor, and Normal severity checks sequentially for token efficiency, producing a PASS or BLOCKED verdict.

Yes, autonomous resolution of BLOCKER findings is supported during the post-build code review. When the gate checks produce a BLOCKED verdict, the system attempts to resolve the findings automatically where possible before requiring manual intervention.

Do not use an automated post-build review gate for spec reviews, planning reviews, or ad-hoc code audits unrelated to a CR. It is specifically designed to validate completed implementation builds after they are finished and requires a CR-ID to function.

During build verification, the review gate handles severity levels by running Critical and High severity checks in parallel for maximum rigor, while running Normal severity checks sequentially for token efficiency. This ensures thorough validation while optimizing resource usage.