requesting-code-review

Automate pre-commit verification by running static security scans and baseline-aware quality gates on local feature branches before committing. This validates code changes, applies linting, and coordinates an independent reviewer subagent to ensure safe merges.

The best way to run quality gates on git diffs is to apply pre-commit verification during feature development. This process executes static security scans, baseline tests, and an auto-fix loop to propose or apply safe fixes before code lands.

Yes, you can configure deterministic skip rules for pre-commit static security scans. This allows you to bypass specific baseline tests or linting checks during local branch verification when certain conditions are met before opening a PR.

Pre-commit verification works directly with git workflows on local branches and PR pipelines. It prepares diffs, runs baseline tests, and coordinates a reviewer subagent to prevent regressions before code merges into the target branch.

The auto-fix loop handles linting errors by proposing or applying safe fixes automatically during pre-commit verification. It runs alongside static security scans and baseline-aware quality gates to clean up code changes before they land in the repository.