dev-requesting-code-review

Automate pre-commit code review by running static security scans, enforcing quality gates, and applying auto-fixes to diffs before code lands. This verifies changes and reports blockers for any regressions across Git commits and pull requests.

Two-stage review in subagent-driven development uses reviewer subagents to validate code changes in sequences, enforcing quality gates and auto-fix loops before committing to ensure baseline tests and linting pass.

Pre-commit verification works with both Git commits and pull requests, running security scans and quality gates across feature and bug-fix workflows to ensure code is safe and clean before landing.

Yes, you need a diff to be present to run static security scans. The pipeline requires a diff to detect changes, run baseline tests, perform linting, and execute optional type checks before reporting regressions.

Yes, you can enforce auto-fix loops for linting and type checks. The pipeline applies auto-fixes and uses reviewer subagents to validate changes, ensuring all quality gates pass before code lands.

Automated code review reports blockers before a Git commit when static security scans, baseline tests, or linting detect regressions or quality gate failures in the diff, preventing unsafe code from landing.