requesting-code-review

Run static scans, quality gates, and independent subagent reviews before commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit code verification: Automated verification pipeline before code lands. Static scans, baseline-aware quality gates, an independent reviewer subagent, and an auto-fix loop. Core principle: No agent should verify its own work. Fresh context finds what you miss.

Core Features & Use Cases

  • Independent review: Initiates automated checks and an autonomous reviewer subagent before commits or pushes.
  • Static analysis & gates: Runs security scans and quality gates to protect code quality.
  • Auto-fix loop: Applies safe auto-fixes where possible and flags remaining issues for manual review.

Quick Start

Run the pre-commit verification workflow on staged changes to ensure they pass all checks.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run automated pre-commit code verification with static scans and quality gates?

Automated pre-commit code verification is performed by running static scans, quality gates, and an autonomous reviewer subagent on staged changes before commits or pushes. It applies safe auto-fixes and flags remaining issues for manual review.

Why does an independent reviewer subagent need to verify code before a git push?

An independent reviewer subagent verifies code before a git push because no agent should verify its own work. Fresh context from an autonomous review process finds missed issues in complex multi-file edits and two-stage reviews that baseline-aware gates might miss.

Can I automatically fix static scan and security violations during a pre-commit hook?

You can automatically fix static scan and security violations during a pre-commit hook using the auto-fix loop. It applies safe auto-fixes where possible to staged changes and flags remaining issues that require manual code review.

What is a baseline-aware quality gate and when do I need it for multi-file edits?

A baseline-aware quality gate is an automated threshold check that evaluates code quality against existing repository standards. You need it for multi-file edits and complex changes across repositories to enforce security checks before commits land.

Does pre-commit static analysis work with complex changes across multiple repositories?

Pre-commit static analysis works with complex changes across multiple repositories by running automated checks, security scans, and quality gates before commits, pushes, and two-stage reviews to ensure comprehensive code verification.