requesting-code-review

Automate pre-commit code review by running static security scans, baseline-aware quality gates, and language-specific linters to validate changes. An independent reviewer subagent and auto-fix loop resolve common issues automatically before commits or pull requests enter the codebase.

An independent reviewer subagent provides extra oversight during pre-commit verification by evaluating code changes separately from the author. It enforces quality gates and reports regressions to ensure robust code quality before commits or pull requests.

Yes, you can automatically scan for secrets and run linters before a GitHub commit. The pre-commit verification workflow performs static security scans and applies language-specific linters to validate changes right after implementation.

You need a two-stage pre-commit verification workflow when 2 or more files are edited or when extra oversight is desired. It coordinates static security scans, quality gates, an independent reviewer subagent, and an auto-fix loop before commits or pushes.

An auto-fix loop handles regressions by automatically resolving common issues found during pre-commit code review. It repeatedly applies fixes, runs quality gates and security scans, and reports remaining regressions to prevent problematic changes from entering the codebase.