requesting-code-review

Verifies code changes before commit with security scans, baseline tests, and independent reviewer subagents.

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

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 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, trigger this Skill before running git commit so the diff is scanned, tested, independently reviewed, and committed with a [verified] prefix only if all gates pass. ## Quick Start Verify my staged changes with the pre-commit review pipeline 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 verify code changes before committing in git?

Run a pre-commit verification pipeline that extracts the git diff, scans added lines for security issues, runs the project's test and lint tools against a baseline, and gets an independent review before committing. This Skill automates that entire sequence and only commits when all gates pass.

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

Pipe git diff output through grep patterns targeting added lines only, matching patterns like api_key assignments, os.system, eval, pickle.loads, and f-string SQL queries. Any match is treated as a security concern that blocks the commit.

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 local diffs, tests, and an independent reviewer subagent. GitHub PR review examines other people's pull requests on GitHub and posts inline comments, which is handled by a separate github-code-review skill.

Does the verification work if my project has no test framework?

Yes. If no test framework is detected, the regression check is skipped and the pipeline still runs the static security scan and independent reviewer verdict. Missing lint tools are also skipped silently without failing the run.

What happens when the automated code review finds issues?

The failures are reported, then a separate fix agent is dispatched to correct only the listed issues without refactoring anything else. The full verification cycle re-runs, and after two failed fix attempts the remaining issues are escalated to the user.

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 commits involving two or more file edits in a git repository.