requesting-code-review

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/superfhp/lumi-agent-body --skill requesting-code-review-superfhp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/superfhp/lumi-agent-body/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/superfhp/lumi-agent-body --skill requesting-code-review-superfhp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code written by an AI agent is often committed without independent verification, letting security flaws, logic errors, and test regressions slip through. This Skill enforces a pre-commit verification pipeline so no agent verifies 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 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 to catch a leaked API key and a broken test, 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 with git?▼

Run git diff --cached to capture staged changes, then scan added lines for secrets and injection patterns, run the project's test suite and linters, and compare failures against a pre-change baseline. Only new failures introduced by your changes should block the commit.

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 command git diff --cached piped to grep for '^+' lines matching credential assignments catches most hardcoded secrets before commit.

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 the repository. GitHub PR review examines other people's pull requests with inline comments after the code is already pushed.

Does this verification work without a test framework installed?▼

Yes, the regression check is skipped when no test framework is detected, and lint checks are skipped silently when tools like ruff or eslint are not installed. The independent reviewer verdict still runs on the diff.

What happens when the automated review finds security issues?▼

The pipeline reports the security concerns and logic errors, then spawns a separate fix agent that addresses only the reported issues. It re-runs the full verification cycle up to two times before escalating remaining issues to the user.