requesting-code-review

Stage your changes with git add, then run this verification pipeline. It extracts the diff via git diff --cached, scans for security issues, runs tests against a baseline, and dispatches an independent reviewer subagent before allowing the commit.

The static scan greps added diff lines for hardcoded secrets and API keys, shell injection via os.system or subprocess shell=True, eval/exec calls, pickle deserialization, and SQL injection through string-formatted queries. Any match is fed to the reviewer as a blocking concern.

This skill verifies your own local changes before committing, while github-code-review comments on other people's PRs on GitHub. Use this one pre-commit; use the GitHub variant for inbound PR review with inline comments.

Yes. If no test framework is detected, the regression check is skipped and the reviewer verdict still runs. Missing lint tools like ruff or eslint are also skipped silently rather than failing the pipeline.

The pipeline allows a maximum of two fix-and-reverify cycles using a separate fix agent. If verification still fails after two attempts, it escalates to the user with the remaining issues and suggests git stash or git reset to undo the changes.