requesting-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written by an agent or developer often ships with security flaws, regressions, or logic errors because the same context that wrote the code cannot objectively review it. This Skill enforces a pre-commit verification pipeline so defects are caught before they land in the repository. ## 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 relative to a stashed 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 touching multiple files, run this pipeline before git commit so a verified change lands with a [verified] commit 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 in git?▼

Stage your changes and run a pre-commit verification pipeline: scan the diff for security patterns, run the project's tests and linters against a baseline, then have an independent reviewer evaluate the diff. Only commit when all checks pass.

How to detect hardcoded secrets in a git diff?▼

Grep the added lines of the diff for patterns like api_key, secret, password, or token assigned to quoted string literals. The pipeline also flags shell injection, eval/exec, pickle.loads, and string-formatted SQL queries in added lines.

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

Pre-commit review verifies your own local changes before they are committed, 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 ruff, mypy, eslint, tsc, clippy, or go vet when installed. Missing tools are skipped silently without failing the run.

What happens when the automated code review finds issues?▼

The pipeline reports the security concerns, logic errors, and regressions, then dispatches a separate fix agent that addresses only the listed issues. It re-runs full verification up to two times, then escalates to the user suggesting 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 asks to skip verification. It is designed for code changes involving two or more file edits in a git repository.