requesting-code-review

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

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/brittb-dev/zerogravityclaw --skill requesting-code-review-brittb-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/brittb-dev/zerogravityclaw/tree/main/src/hermes-core/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/brittb-dev/zerogravityclaw --skill requesting-code-review-brittb-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get committed without independent verification, letting security vulnerabilities, logic errors, and test 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 injection patterns. - Baseline-Aware Quality Gates: Runs pytest, npm test, cargo test, or go test plus linters like ruff, mypy, eslint, and clippy, comparing failures against a pre-change baseline so only new regressions block the commit. - Independent Reviewer and Auto-Fix Loop: Dispatches a fresh-context reviewer subagent that returns a fail-closed JSON verdict, then spawns a separate fix agent for up to two fix-and-reverify cycles before committing with a [verified] prefix. - Use Case: After implementing a bug fix touching three files, run this pipeline before git push to catch a leftover debug statement and a new lint error, auto-fix them, and commit only after the independent reviewer passes. ## Quick Start Ask the agent to verify and review your staged changes before committing, for example by saying "review my changes before merge".

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 on the git diff. It scans added lines for security issues, runs tests and linters against a pre-change baseline, and gets an independent reviewer verdict before allowing the commit.

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

The static scan detects hardcoded secrets and API keys, shell injection via os.system or subprocess shell=True, eval and exec calls, unsafe pickle deserialization, and SQL injection from string-formatted queries. Any match automatically fails the review.

Does this work with Python, Node, Rust, and Go projects?▼

Yes, it auto-detects the project language and runs the appropriate tools: pytest, ruff, and mypy for Python; npm test, eslint, and tsc for Node; cargo test and clippy for Rust; and go test with go vet for Go. Missing tools are skipped silently.

What is the difference between requesting-code-review and github-code-review?▼

requesting-code-review verifies your own uncommitted changes locally before git commit or push. github-code-review reviews other people's pull requests on GitHub with inline comments, which is a separate workflow.

What happens when the automated code review fails?▼

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, remaining issues are escalated to the user with suggestions to git stash or git reset.

When should I skip pre-commit verification?▼

Skip it for documentation-only changes, pure configuration tweaks, or when the user explicitly says to skip verification. It is designed for code changes involving two or more file edits in a git repository.