requesting-code-review

Automate pre-commit verification with static security scans and quality gates.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/tangzheng202202/hermes-skills --skill requesting-code-review-tangzheng202202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/tangzheng202202/hermes-skills/tree/main/01-coding-dev/software-development/requesting-code-review
Command: npx skills add https://github.com/tangzheng202202/hermes-skills --skill requesting-code-review-tangzheng202202

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR. Core principle: No agent should verify its own work; fresh context helps catch what you miss.

Core Features & Use Cases

  • Static security scans on diffs to surface secrets and insecure patterns.
  • Baseline-aware quality gates with automated linting and tests.
  • Independent reviewer subagent that validates changes before merge.
  • Auto-fix loop that can apply non-breaking improvements to the diff before commit.
  • Works before commits, pushes, or PRs across multi-file edits and team workflows.

Quick Start

Run the pre-commit verification on your current changes to ensure the diff passes static checks and tests 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 automate pre-commit code review and security scanning for my Git changes?▼

Automated pre-commit code review runs static security scans and quality gates on your Git diffs, using an independent reviewer subagent and an auto-fix loop to apply non-breaking improvements before you commit or push.

What is an independent reviewer subagent and how does it validate code before merge?▼

An independent reviewer subagent validates code before merge by using a fresh context to review diffs, operating on the principle that no agent should verify its own work, ensuring baseline tests and linting pass safely.

How do I run static security scans and linting on multi-file Git diffs before pushing?▼

Static security scans and linting run on multi-file Git diffs before pushing by validating changes against baseline-aware quality gates, automatically surfacing secrets and insecure patterns across single-repo and PR workflows.

Can I automatically fix linting and security issues in a pre-commit Git hook?▼

You can automatically fix linting and security issues in a pre-commit Git hook using an auto-fix loop that applies non-breaking improvements to the diff, ensuring changes pass quality gates before commit.

Does automated pre-commit verification work with both single-repo and PR workflows?▼

Automated pre-commit verification works with both single-repo and PR workflows, supporting multi-file edits across Git workflows by validating diffs, running baseline tests, and enforcing safe review practices after feature or bug fix changes.

When should I run pre-commit verification with static security scans and auto-fix?▼

Run pre-commit verification with static security scans and auto-fix after completing feature or bug fix code changes and before committing, pushing, or opening a PR to ensure all diffs pass baseline tests and linting.