requesting-code-review

Pre-commit verification inspects staged git diffs to block commits introducing new security or logic failures. It runs targeted static security scans, baseline-aware test comparisons, and an independent reviewer subagent before allowing the commit.

Baseline-aware testing compares project test and lint failures before and after your changes. This ensures only new regressions introduced by the current diff block the commit, allowing pre-existing issues to pass without manual filtering.

Yes, targeted static security scans inspect added lines in your git diff to detect hardcoded secrets, shell injection patterns, unsafe deserialization, and parameterized SQL requirements before the commit is finalized.

An independent reviewer subagent evaluates the diff and scan results, enforcing fail-closed JSON verdicts. It triggers an auto-fix loop that runs up to two precise fix cycles before escalating unresolved issues.

The pipeline applies targeted static security scans and linters directly to the git diff. It acts as an independent verification layer that complements your existing tools by comparing baseline results against new changes.

The auto-fix loop runs up to two precise fix cycles. If the independent reviewer subagent cannot resolve the failures within these cycles, it escalates the unresolved security or logic issues for manual intervention.