requesting-code-review

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

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

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 checks it. 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), comparing against a pre-change baseline so only new failures block the commit. - Independent Reviewer and Auto-Fix Loop: Dispatches a fresh-context reviewer subagent that returns a fail-closed JSON verdict, then a separate fix agent that corrects only reported issues across up to two re-verification cycles. - Use Case: After implementing a bug fix touching three files, run this pipeline before git push to catch a leaked API key and a new test regression, auto-fix them, and commit with a [verified] prefix. ## Quick Start Verify my staged changes with the pre-commit review pipeline and fix any issues before committing.

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 in git?▼

Run a pre-commit verification pipeline that scans the staged diff for security issues, runs tests and linters against a pre-change baseline, and dispatches an independent reviewer subagent. Only new failures introduced by your changes block the commit.

How to detect hardcoded secrets in a git diff?▼

Grep added lines from git diff --cached for patterns like api_key, secret, password, or token assigned to quoted strings of six or more characters. Any match is treated as a security concern that fails verification.

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

Pre-commit review verifies your own local changes before committing, using static scans and an independent reviewer subagent. GitHub PR review examines other people's pull requests and posts inline comments on the platform.

Does the verification pipeline work with Python, Node, Rust, and Go projects?▼

Yes, it auto-detects the project language and runs the appropriate tools: pytest, npm test, cargo test, or go test, plus linters like ruff, mypy, eslint, clippy, and go vet when installed. Missing tools are skipped silently without failing.

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

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

When should I skip pre-commit code verification?▼

Skip verification for documentation-only changes, pure configuration tweaks, or when the user explicitly says to skip it. The pipeline also exits early when the diff is empty or the directory is not a git repository.