requesting-code-review

Run a pre-commit verification pipeline that extracts the git diff, scans added lines for security patterns, runs baseline tests and linters, then dispatches an independent reviewer subagent. Only commits that pass all checks receive a [verified] prefix.

The static scan detects hardcoded secrets and API keys, shell injection via os.system or subprocess shell=True, eval/exec usage, unsafe pickle deserialization, and SQL injection through string-formatted queries. Any match is fed to the reviewer as a security concern.

Pre-commit review verifies your own local changes before they are committed or pushed, using the local git diff. GitHub code review examines other people's pull requests on the remote platform and posts inline comments.

Yes. If no test framework is detected, the regression check is skipped and the reviewer verdict still runs. Missing lint tools are also skipped silently without failing the pipeline.

Failures trigger an auto-fix loop where a separate fix agent addresses only the reported security concerns and logic errors, then the full verification cycle re-runs. After two failed attempts, the issues are escalated to the user with suggestions to stash or reset.

Skip verification for documentation-only changes, pure configuration tweaks, or when the user explicitly requests it. The pipeline targets substantive code changes, typically tasks with two or more edited files in a git repository.