requesting-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit verification of code changes to catch issues before they are committed, pushed, or opened as a PR.

Core Features & Use Cases

  • Static security scans, baseline-aware quality gates, and an independent reviewer subagent to validate changes.
  • Auto-fix loop to address common issues and maintain code quality before landing.

Quick Start

Run the pre-commit verification workflow on your current diff to ensure all checks pass 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 run pre-commit code review checks on my current git diff?

Pre-commit code review checks run static security scans and quality gates directly on your current diff. An independent reviewer subagent validates the changes, and an auto-fix loop addresses common issues before allowing the commit to proceed.

Can I automate static security scans before pushing code?

Static security scans are fully automated as part of the pre-commit verification workflow. The process catches security issues in your code changes before they are committed, pushed, or opened as a pull request.

What are baseline-aware quality gates in a code review workflow?

Baseline-aware quality gates enforce code quality standards relative to your project's existing baseline during the pre-commit review cycle. They ensure only validated changes proceed, preventing regressions from landing in the repository.

Does the pre-commit review agent provide an auto-fix loop for failing checks?

The pre-commit review agent includes an auto-fix loop to automatically address common issues found during static security scans and quality gate checks. This maintains code quality and resolves failures before changes proceed to commit.

How do I prevent bad code from being committed using git pre-commit hooks?

Pre-commit verification gates block bad code from being committed by running static security scans and an independent reviewer subagent. Only changes that successfully pass all validation checks are allowed to proceed to commit, push, or open a PR.