requesting-code-review

Review staged Git changes with security scans and quality gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically enforces security, quality gates, and automated review before code lands, preventing risky changes from reaching main branches.

Core Features & Use Cases

  • Static security scans: detect hardcoded secrets, dangerous eval/execution, or unsafe deserialization in staged changes.
  • Baseline-aware quality gates: compare against project baselines to ensure standards are met before commit or push.
  • Independent reviewer subagent: adds an impartial review step that can be triggered after initial changes.
  • Auto-fix loop: auto-fix common issues when safe to do so, reducing manual rework.

Quick Start

Run the pre-commit verification on the current staged changes.

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 a pre-commit code review on staged Git changes?

Pre-commit code review involves verifying staged Git changes before they land by applying static security scans and baseline quality gates. It prevents risky commits from reaching main branches by detecting hardcoded secrets and enforcing standards early.

Can pre-commit checks automatically fix security issues like hardcoded secrets?

Pre-commit checks can auto-fix common security issues like hardcoded secrets and unsafe deserialization using a safe auto-fix loop. This reduces manual rework by automatically resolving detected vulnerabilities during the static scan without introducing new problems.

How do baseline-aware quality gates work for Git commits?

Baseline-aware quality gates compare staged changes against project baselines to ensure standards are met before commit or push. This prevents quality regressions by blocking code that falls below the established project baseline.

Does the independent reviewer subagent provide impartial code review before commit?

The independent reviewer subagent provides impartial code review before commit by adding an automated, neutral review step. Triggered after initial staged changes, it independently verifies security and quality without human bias.

What are the limitations of automated pre-commit static security scans?

Automated pre-commit static security scans are limited to detecting known patterns like hardcoded secrets and unsafe deserialization in staged changes. They rely on safe auto-fix loops that strictly avoid introducing new issues during automated remediation.