full-review

A comprehensive code review before merging automates parallel audits for security, correctness, code quality, and documentation accuracy. This approach orchestrates four specialized audit lenses simultaneously to generate separate, unedited reports for each category without manual intervention.

A quality gate in automated code review is a multi-lens verification process that checks security, correctness, code quality, and documentation accuracy. It works by running parallel audit skills that generate domain-specific reports, ensuring high-confidence verification before code merges.

Yes, you can automate security audits and documentation checks simultaneously through parallel audit orchestration. This capability runs code-review, anti-slop, security-audit, and update-docs checks concurrently to minimize wait times and produce context-aware, actionable reports.

Parallel audit orchestration does not cross-edit or merge findings from different checks. It generates separate, unedited reports for each audit lens, ensuring the findings remain domain-specific, context-aware, and immediately actionable for developers.

You need a multi-lens quality gate when performing pre-merge checks on major feature branches. It satisfies requirements for high-confidence verification by catching bugs, security vulnerabilities, stale documentation, and code quality issues in a single automated pass.

The best way to catch stale documentation and security vulnerabilities before a merge is a comprehensive pre-merge reflex check. This automated process targets software engineering workflows by running parallel audits that produce separate reports for code quality and documentation accuracy.