requesting-code-review

Automated pre-commit verification runs static security scans, baseline-aware quality gates, and an independent reviewer subagent on your code changes before git commit or push to ensure quality and security.

An independent reviewer subagent operates with fresh context to evaluate your code changes, strictly enforcing the core principle that no agent should verify its own work, which helps catch issues missed during initial implementation.

You should skip pre-commit verification for documentation-only changes, pure config tweaks, or when explicitly requested to skip, focusing the automated security scans and quality gates on substantive code edits.

The best way to automate pre-commit checks is using a pipeline that performs static security scans, baseline-aware quality gates, and an auto-fix loop to detect and resolve issues before merging or pushing code.

Trigger automated code verification after implementing features or bug fixes, after completing a task with two or more file edits in a git repo, or when requesting a review before merge to ensure baseline quality.

Pre-commit verification supports multiple languages and tooling to execute static security scans, run tests, perform linting, and apply auto-fixes across diverse codebases before committing changes.