requesting-code-review

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

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill requesting-code-review-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/CHENHUI-X/toolbox/tree/main/official-skills/software-development/requesting-code-review
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill requesting-code-review-chenhui-x

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. This Skill enforces a pre-commit verification pipeline so no agent (or developer) approves 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 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 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 in git?

Stage your changes with git add, then run a verification pipeline that scans the diff for security issues, runs tests against a pre-change baseline, and gets an independent review. This Skill automates that entire flow and commits with a [verified] prefix on success.

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

Pipe git diff --cached through grep patterns targeting added lines: match api_key/secret/password assignments, os.system, subprocess with shell=True, eval/exec, pickle.loads, and f-string SQL queries. Any match is treated as a blocking security concern.

Does this code review 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 automated code review finds failures?

Failures trigger an auto-fix loop: a separate fix agent corrects only the reported security concerns and logic errors, then the full verification cycle re-runs. After two failed attempts, the issues are escalated to the user with suggestions to git stash or 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 of two or more files in a git repository before commit or push.