requesting-code-review

Scan staged Git diffs for security risks and regressions before commit.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents insecure or low-quality changes from being committed by automatically scanning your staged diff, checking for regressions, and running an independent review that fails the commit on detected issues.

Core Features & Use Cases

  • Pre-commit security scanning: Flags likely hardcoded secrets, shell injection patterns, dangerous eval/exec usage, unsafe deserialization, and common SQL-injection string formatting hazards from added lines.
  • Baseline-aware quality gates: Detects the project type and runs appropriate tests and optional lint/type checks, blocking only newly introduced failures by comparing against a pre-change baseline.
  • Fail-closed independent reviewer + auto-fix loop: Delegates an isolated reviewer that returns strictly valid JSON verdicts, and—if needed—runs a limited fix-and-reverify cycle to address only reported issues.
  • Use case: After finishing a feature branch change in a Git repository with 2+ edited files, run the verification before committing so you catch mistakes early.

Quick Start

Ask the AI to run the pre-commit verification for your staged changes in the current Git repository before you 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 a pre-commit code review on my staged Git diff?

A pre-commit code review scans your staged Git diff for hardcoded secrets and injection hazards, runs baseline-aware tests, and delegates an independent reviewer to block commits with detected issues.

Can I automatically fix security vulnerabilities before committing code?

You can automatically fix security vulnerabilities before committing using an optional two-cycle auto-fix-and-reverify loop that addresses only reported issues and re-verifies the staged diff.

Does pre-commit security scanning detect hardcoded secrets and SQL injection?

Pre-commit security scanning detects hardcoded secrets and SQL injection by flagging shell injection patterns, dangerous eval/exec usage, unsafe deserialization, and common SQL-injection string formatting hazards from added lines.

What is baseline-aware regression testing for pre-commit verification?

Baseline-aware regression testing for pre-commit verification detects your project type, runs tests and lint checks, and blocks only newly introduced failures by comparing against a pre-change baseline.

When should I use an independent reviewer with fail-closed JSON for code review?

Use an independent reviewer with fail-closed JSON for code review during feature completion, multi-file edits, and pre-merge verification scenarios where regressions and security risks must be blocked before committing.