requesting-code-review

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

Verify staged git changes for security issues and regressions before commit.

1|Updated Apr 10, 2026

Search Tags:#git #code review #auto-fix #pre-commit #regression testing #security scanning

Ready to run

npx skills add https://github.com/zerwiz/wayofpi --skill requesting-code-review-zerwiz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents low-quality or risky code from reaching commit history by running a pre-commit verification pipeline that checks security, correctness, and regressions before you ship.

Core Features & Use Cases

Static Security Scanning: Detects hardcoded secrets, shell injection, unsafe eval or exec usage, unsafe deserialization, and SQL injection patterns in the staged diff.
Baseline-Aware Testing: Runs the project’s available test and lint tools, then compares failures against the pre-change baseline so only new regressions block progress.
Independent Review and Auto-Fix Loop: Sends the diff to a separate reviewer subagent, then iterates on targeted fixes when security or logic issues are found.
Use Case: Before opening a pull request, use this Skill to confirm your changes are safe, tested, and ready for commit without self-review bias.

Quick Start

Use the requesting-code-review skill to verify the staged changes in this repository 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 code review and security scanning before a git commit?▼

You can automate pre-commit code review by running a verification pipeline that inspects staged git diffs for security issues, logic errors, and regression risk before you push. This ensures unsafe changes are caught early by scanning for hardcoded secrets and injection patterns.

What is baseline-aware regression testing and how does it work with staged changes?▼

Baseline-aware regression testing runs your project's available test and lint tools, then compares failures against the pre-change baseline. This ensures only new regressions introduced by your staged code changes block progress, preventing pre-existing test failures from halting your commit.

How can I detect hardcoded secrets and SQL injection patterns in my staged diff?▼

Static security scanning detects hardcoded secrets, shell injection, unsafe eval or exec usage, and SQL injection patterns by inspecting the staged diff. This verifies that security vulnerabilities are identified and resolved before the code reaches commit history.

Can I use an independent reviewer subagent to auto-fix logic errors in my code?▼

Yes, you can send the diff to a separate reviewer subagent that iterates on targeted fixes when security or logic issues are found. This independent review and auto-fix loop eliminates self-review bias and confirms the change is safe to land.

Does pre-commit verification work with multi-file edits in git-based workflows?▼

Pre-commit verification applies to git-based software development workflows that need independent validation of multi-file edits. It requires diff inspection, static scanning, test execution, and lint checks to confirm the entire staged change set is safe to commit.

When should I run a pre-commit code review pipeline instead of waiting for pull request feedback?▼

You should run a pre-commit code review pipeline before opening a pull request to confirm your changes are safe, tested, and ready without self-review bias. This prevents low-quality or risky code from reaching commit history and blocking your PR later.