requesting-code-review

Verifies code changes before commit using static scans, baseline tests, and an independent reviewer subagent.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill requesting-code-review-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill requesting-code-review-mlt-oss

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 Scan: 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 versus the pre-change baseline. - Independent Reviewer Subagent: Delegates the diff to a fresh-context reviewer 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 before escalating to the user, then commits with a [verified] prefix. - Use Case: After implementing a feature touching multiple files, run this pipeline before git commit to catch a leaked API key and a broken test that self-review would have missed. ## 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 verify code changes before committing with an AI agent?

Run a pre-commit pipeline that scans the git diff for security issues, runs tests against a pre-change baseline, and dispatches an independent reviewer subagent. Only new failures block the commit, and an auto-fix loop attempts up to two repair cycles.

How to detect hardcoded secrets in a git diff?

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

What is the difference between this skill and github-code-review?

This skill verifies your own changes locally before committing, using static scans and a reviewer subagent. github-code-review reviews other people's pull requests on GitHub and posts inline comments.

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

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

What happens when the auto-fix loop keeps failing?

The loop allows a maximum of two fix-and-reverify cycles. If verification still fails after both attempts, the pipeline escalates to the user with the remaining issues and suggests git stash or git reset to undo the changes.

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