requesting-code-review

Scan git diffs for security and quality issues before commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit verification prevents faulty or insecure changes from landing by enforcing security scans, quality gates, and an automated fix loop before commits.

Core Features & Use Cases

  • Static diff analysis and security scans on staged changes prior to commit or push
  • Baseline tests, linting, and type checks to maintain code quality
  • Independent reviewer subagent workflow with an auto-fix loop to remediate issues and improve future commits

Quick Start

Run the pre-commit verification on the current changes to ensure security, quality gates, and auto-fix are applied before commit.

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 security scans and linting on staged git changes before committing?

Pre-commit verification runs static security scans and linting on staged git changes to identify and reject commits that introduce security or quality issues before they land.

Can I use automated code review to block insecure pull requests from being merged?

Yes, applying pre-commit verification to PR workflows across git diffs ensures every staged change passes baseline tests, static analysis, and an independent reviewer subagent before landing.

What is a pre-commit quality gate and how does it prevent faulty code from landing?

A pre-commit quality gate enforces security scans, baseline tests, and linting on local commits and PR workflows, rejecting changes that introduce vulnerabilities or quality issues before they land.

Does the pre-commit code review workflow include an auto-fix loop for detected issues?

Yes, the verification workflow uses a two-stage independent reviewer subagent with an auto-fix loop to remediate detected security and quality issues and improve future commits.

Do I need external dependencies to run static analysis checks on my git diff?

No, the pre-commit verification operates independently without external dependencies, applying static diff analysis, security scans, linting, and type checks directly to your staged changes.

When should I not use a pre-commit hook for static security scanning?

If your project requires merging changes rapidly without enforcing baseline tests or quality gates, the pre-commit verification's auto-fix loop and scan enforcement will block commits and slow down the workflow.