requesting-code-review

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

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

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 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 two fix-and-reverify cycles before escalating to the user. - Use Case: After implementing a feature across several files, run this pipeline before git commit so an independent reviewer approves the diff and the commit is tagged with a [verified] prefix. ## 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 review code changes before committing with git?

Run this pre-commit verification pipeline on your staged 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 committing with a [verified] prefix.

What security issues does a pre-commit code scan detect?

The 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.

How is this different from reviewing GitHub pull requests?

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 and the GitHub one for inbound PR review.

Does the verification work if my project has no tests?

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 automated review finds problems?

Failures trigger an auto-fix loop where a separate fix agent corrects 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.

When should I skip pre-commit verification?

Skip it for documentation-only changes, pure configuration tweaks, or when you explicitly say to skip verification. It is designed for code changes of two or more files in a git repository.