requesting-code-review

Automate pre-commit code review by applying static security scans, baseline-aware quality gates, and an independent reviewer subagent to validate changes before committing. This workflow runs locally to surface issues and apply automatic fixes before code reaches the main branch.

Baseline-aware quality verification evaluates code changes against existing project standards using static security scans and a policy engine. It ensures fail-closed guidance by blocking commits that do not meet baseline security and quality requirements before they are pushed.

Yes, you can use static security scans with an auto-fix loop to address common issues automatically before pushing. The system attempts to resolve detected vulnerabilities while preserving developer intent, providing fail-closed guidance if verification does not pass.

Yes, pre-commit code verification requires configured scanners, a policy engine, and a defined workflow to produce fail-closed results. These components are necessary to execute static security scans, apply quality gates, and trigger the auto-fix loop across multi-file changes.

Run pre-commit code review after making code changes and before committing, pushing, or opening pull requests. It is specifically designed to validate multi-file changes locally, ensuring static security scans and independent reviewer checks pass before integration.