requesting-code-review

Run static security scans and quality gates on Git diffs before committing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/adm-humanerd/drewgent --skill requesting-code-review-adm-humanerd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/adm-humanerd/drewgent/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/adm-humanerd/drewgent --skill requesting-code-review-adm-humanerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.

Core Features & Use Cases

  • Static security scans on diffs to surface secrets, risky patterns, and potential vulnerabilities before they are committed.
  • Baseline-aware quality gates to ensure consistency with project standards and prevent regressions.
  • Independent reviewer subagent to provide impartial code reviews and reduce self-review risk.
  • Auto-fix loop that suggests or applies safe fixes to common issues during verification.
  • Use Case: After implementing a feature or bug fix, run the verification before committing or pushing to catch issues early and maintain PR quality.

Quick Start

Run the pre-commit verification after you modify code and before committing or pushing to ensure changes meet security and quality standards.

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 pre-commit code review and security scans on my staged Git diff?▼

Pre-commit code review automates verification by running static security scans and baseline-aware quality gates on staged Git diffs. It analyzes the changes before committing or opening a pull request to surface secrets, risky patterns, and potential vulnerabilities early.

What is the best way to prevent code quality regressions before pushing to a remote repository?▼

Preventing code quality regressions before pushing requires baseline-aware quality gates that enforce project standards. The verification process checks staged diffs against established baselines, ensuring consistency and preventing regressions from reaching the remote repository.

Can I automatically fix common code issues found during a pre-commit security scan?▼

Yes, an auto-fix loop can suggest or apply safe fixes to common issues found during pre-commit security scans. This loop operates during the verification process, providing deterministic feedback and resolving detected vulnerabilities before code is committed.

Does the independent reviewer subagent replace manual pull request reviews?▼

The independent reviewer subagent supplements manual pull request reviews by providing impartial code analysis and reducing self-review risk. It operates deterministically on staged diffs to catch issues early, maintaining PR quality before human reviewers evaluate the changes.

How does baseline-aware verification handle existing code when scanning a staged diff?▼

Baseline-aware verification compares staged diffs against existing project standards rather than scanning the entire repository. This ensures the security scans and quality gates focus only on the new changes, preventing regressions while respecting established code baselines.