code-review

Code quality audits for sub-agent outputs are automated by triggering post-implementation reviews with commands like 'compile passed', enforcing status verification, review execution, and report generation.

A code review workflow checks sub-agent generated code for quality, conformance, and boundary checks during post-implementation reviews, outputting detailed audit reports and fix proposals when issues are found.

To generate a code review report, trigger the review process after sub-agent implementation passes compilation; the workflow executes mandatory steps from scope collection to report generation and fix proposal creation.

Yes, you can enforce mandatory steps for code conformance and boundary checks by triggering the automated review workflow, which verifies status, collects scope, and executes audits before generating reports.

The best way to handle code boundary violations is using an automated review workflow that detects issues during audits and creates specific fix proposals for subsequent user confirmation and resolution.

You need an automated code review report when sub-agent implementation is complete and compilation passes, ensuring quality, conformance, and boundary checks are verified before final user confirmation.