requesting-code-review

Verifies staged git changes for security issues and quality regressions before committing.

87|20|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/openaeon/OpenAEON --skill requesting-code-review-openaeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/openaeon/OpenAEON/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/openaeon/OpenAEON --skill requesting-code-review-openaeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents insecure or regression-prone changes from being committed by running a pre-commit verification pipeline with static security scanning, baseline-aware tests/linting, and an independent reviewer step.

Core Features & Use Cases

  • Diff-first security scanning: flags high-risk patterns in newly added lines (e.g., secrets, command injection, eval/exec, unsafe deserialization, SQL injection string formatting).
  • Baseline-aware quality gates: captures existing failure counts before your changes and blocks only new failures/regressions.
  • Independent reviewer subagent: evaluates the diff and scan results in a fail-closed manner to reduce self-review bias, then optionally triggers a targeted auto-fix loop.

Quick Start

Use requesting-code-review right after you finish editing code in a git repo and have a staged diff, asking the AI to verify before you run git 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 security scan on my staged git diff before committing?

Pre-commit security scanning flags high-risk patterns like secrets, command injection, and unsafe deserialization in newly added lines of your staged git diff before you commit.

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

Baseline-aware regression testing captures existing failure counts before your changes and blocks only new failures, preventing pre-commit checks from failing on pre-existing issues.

How do I prevent self-review bias when checking code changes before a git push?

An independent reviewer subagent evaluates your diff and scan results in a fail-closed manner to reduce self-review bias, optionally triggering a targeted auto-fix loop for code changes before a git push.

Can I automatically fix security issues found in staged git changes?

Yes, an optional limited auto-fix loop can automatically resolve security issues and quality regressions found during deterministic diff scanning of staged git changes before you commit.

Does this pre-commit code review tool work with existing static analysis and linting?

Yes, this pre-commit code review tool integrates with existing static analysis and linting by capturing baseline failure counts and blocking only new regressions introduced by your staged git diff.