requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: zangjeicy

Scan git diffs for security vulnerabilities and quality regressions.

Updated Jul 13, 2026

Search Tags:#security #verification #quality #auto-fix #pre-commit #code-review

Ready to run

npx skills add https://github.com/zangjeicy/Hermes --skill requesting-code-review-zangjeicy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/zangjeicy/Hermes/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/zangjeicy/Hermes --skill requesting-code-review-zangjeicy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the introduction of security vulnerabilities, logic errors, and regressions into your codebase by enforcing an automated, independent verification pipeline before any code is committed.

Core Features & Use Cases

Automated Security Scanning: Detects hardcoded secrets, shell injections, and unsafe deserialization patterns in real-time.
Baseline-Aware Quality Gates: Runs linting and test suites, comparing results against a baseline to ensure only new changes are scrutinized.
Independent Reviewer Subagent: Employs a secondary, isolated AI agent to perform a logic-focused code review, ensuring a fresh perspective on your changes.

Quick Start

Ask the agent to verify your current changes before you commit them to the repository.

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 security scanning on git diffs before committing?▼

Automated security scanning on git diffs detects hardcoded secrets, shell injections, and unsafe deserialization. It enforces pre-commit validation by executing static analysis tools directly in the terminal to prevent vulnerabilities from entering the codebase.

What is baseline-aware quality verification for pre-commit hooks?▼

Baseline-aware quality verification runs linting and test suites against git diffs, comparing results against existing baselines. This ensures only new changes are scrutinized, preventing regressions while focusing validation on uncommitted code.

Can I use an independent AI subagent for logic-focused code review?▼

Yes, an independent reviewer subagent performs logic-focused code review in isolation. This secondary AI agent provides a fresh perspective on uncommitted changes, ensuring an automated verification pipeline catches logic errors before commit.

Does pre-commit code review require terminal access to execute git commands?▼

Yes, pre-commit security and quality verification requires terminal access to execute git commands, static analysis tools, and test frameworks. This environment enables the automated scanning pipeline to validate diffs directly.

What's the best way to prevent security vulnerabilities and regressions in a software development workflow?▼

The best way to prevent vulnerabilities and regressions is enforcing an automated, independent verification pipeline before commit. This applies baseline-aware quality gates and security scanning to git diffs, catching issues during development.

Why should I use an isolated subagent for code review instead of standard linting?▼

An isolated subagent for code review provides a secondary, independent perspective focused on logic. Standard linting catches syntax errors, but the subagent ensures logic-focused verification prevents deeper errors from entering the codebase.