requesting-code-review

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

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/i-bebsi/hermes-agent --skill requesting-code-review-i-bebsi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/i-bebsi/hermes-agent/tree/main/hermes-config/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/i-bebsi/hermes-agent --skill requesting-code-review-i-bebsi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get committed without independent verification, letting security flaws, logic errors, and regressions slip through because the same agent that wrote the code also reviews it. ## Core Features & Use Cases - Static Security Scanning: Greps added diff lines for hardcoded secrets, shell injection, eval/exec, unsafe pickle deserialization, and SQL string formatting. - 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 before escalating to the user, then commits with a [verified] prefix. - Use Case: After implementing a feature touching multiple files, run this pipeline before git push to catch a leaked API key and a missing error handler that self-review would have missed. ## Quick Start Ask the agent to verify and review my staged changes before committing them.

Frequently Asked Questions about requesting-code-review

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

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

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

What security issues does pre-commit code review detect?▼

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, unsafe pickle deserialization, and SQL injection through string-formatted queries.

How is this different from GitHub pull request code review?▼

This skill verifies your own local changes before committing, while github-code-review comments on other people's pull requests on GitHub. Use this one pre-commit and the GitHub skill for PR review workflows.

Does the verification work if my project has no tests?▼

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

What happens when the automated code review fails?▼

Failures trigger an auto-fix loop where a separate fix agent addresses only the reported issues, then the full verification re-runs. After two failed cycles, the remaining issues are escalated to you with suggestions to stash or reset.

Why does the reviewer subagent return a failed verdict unexpectedly?▼

The reviewer operates fail-closed: any security concern, logic error, or unparseable diff forces passed to false. If it flags something intentional, note that context in the fix prompt to resolve the false positive.