requesting-code-review

Verifies git diffs with security scans, baseline tests, and an independent reviewer subagent before commit.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Junkfooooood/hermes-governance --skill requesting-code-review-junkfooooood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Junkfooooood/hermes-governance/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/Junkfooooood/hermes-governance --skill requesting-code-review-junkfooooood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written by an AI agent is often committed without independent verification, letting security flaws, logic errors, and regressions slip through. This Skill enforces a pre-commit verification pipeline so no agent verifies its own work. ## Core Features & Use Cases - Static Security Scanning: Greps added diff lines for hardcoded secrets, shell injection, eval/exec, unsafe pickle deserialization, and SQL injection patterns. - Baseline-Aware Quality Gates: Runs pytest, npm test, cargo test, or go test plus linters (ruff, mypy, eslint, clippy, go vet) and only blocks on NEW failures versus the pre-change baseline. - Independent Reviewer Subagent: Dispatches a fresh-context reviewer via delegate_task that returns a fail-closed JSON verdict on security concerns and logic errors. - Auto-Fix Loop: Spawns a separate fix agent for up to 2 fix-and-reverify cycles, then commits with a [verified] prefix on success. - Use Case: After implementing a feature across several files, say "verify before commit" and the pipeline scans the diff, runs tests, gets an independent review, fixes any findings, and commits only when everything passes. ## Quick Start Verify my staged changes with the pre-commit review pipeline and commit them if everything passes.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes before committing with git?

Stage your changes with git add, then run the verification pipeline: it extracts the diff with git diff --cached, scans added lines for security issues, runs tests and linters against a pre-change baseline, and gets an independent reviewer verdict before committing.

How to scan a git diff for hardcoded secrets and SQL injection?

Pipe git diff --cached through grep on added lines only, matching patterns like api_key or password assignments, os.system, subprocess with shell=True, eval/exec, pickle.loads, and f-string SQL queries. Any match is fed to the reviewer as a blocking security concern.

What is the difference between pre-commit review and GitHub PR review?

Pre-commit review verifies your own local changes before they are committed, using local diffs, tests, and an independent subagent. GitHub PR review examines other people's pull requests on the platform and posts inline comments.

Does the verification pipeline work if no test framework is installed?

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

What happens when the auto-fix loop cannot resolve review failures?

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