requesting-code-review

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill requesting-code-review-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill requesting-code-review-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code changes often get committed without independent verification, letting security flaws, regressions, and lint errors slip through. This Skill enforces a pre-commit verification pipeline so no agent (or developer) verifies its own work unchecked. ## Core Features & Use Cases - Static Security Scanning: Greps staged diffs 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, tsc, 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 reported issues, with a maximum of 2 fix-and-reverify cycles before escalating to the user. - Use Case: After implementing a feature touching multiple files, run this pipeline before git commit to catch a leaked API key and a new ruff violation, 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 on the staged diff from git diff --cached. It scans added lines for security issues, runs tests and linters against a pre-change baseline, and dispatches an independent reviewer before allowing the commit.

How to scan git diffs for hardcoded secrets and security issues?▼

Grep added lines in the staged diff for patterns like api_key, secret, password, or token assignments, plus os.system, subprocess shell=True, eval, exec, pickle.loads, and string-formatted SQL queries. Any match is treated as a blocking security concern.

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

Pre-commit review verifies your own uncommitted changes locally before they land in git history. GitHub PR review examines other people's pull requests with inline comments after the code is already pushed.

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, ruff, and mypy for Python; npm test, eslint, and tsc for Node; cargo test and clippy for Rust; go test and go vet for Go. Missing tools are skipped silently.

Why does ruff report invalid-syntax on nested f-strings?▼

Python versions before 3.12 cannot reuse the same quote character in nested f-strings, so ruff flags it as invalid-syntax. The fix is to extract the inner f-string into a variable before embedding it in the outer f-string; ruff cannot auto-fix this.

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 issues remain after both attempts, it escalates to the user with the remaining problems and suggests git stash or git reset to undo the changes.