requesting-code-review

Generate a pre-commit verification pipeline that scans staged diffs and obtains fail-closed JSON reviews.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill requesting-code-review-zardli1115
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill requesting-code-review-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or insecure code from being committed by running security scans, quality gates, and an independent review before changes land.

Core Features & Use Cases

  • Security scan on added code: flags likely secrets, shell/command injection patterns, eval/exec, unsafe deserialization, and basic SQL injection formatting risks.
  • Baseline-aware tests and linting: captures existing failure counts as a baseline so only new regressions block the commit.
  • Independent reviewer + bounded auto-fix: delegates the diff to a separate reviewer for a fail-closed JSON verdict, then optionally runs a limited fix-and-reverify loop.

Quick Start

Ask the agent to verify your staged changes before commit by saying: "Review and auto-fix my diff before I 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 security scans and lint checks on staged git changes before committing?

Pre-commit code checks scan staged git diffs to detect insecure patterns like secrets and command injection, then run baseline-aware tests and lint checks to block low-quality commits.

How does baseline-aware test gating work for pre-commit verification pipelines?

Baseline-aware test gating captures existing test failure counts before your changes, ensuring only new regressions introduced by the staged diff block the commit rather than pre-existing issues.

Can I automatically fix insecure code detected by a pre-commit security scan?

Yes, the pre-commit pipeline delegates the diff to an independent reviewer for a fail-closed JSON verdict and optionally runs up to two bounded fix-and-reverify cycles to auto-fix issues.

What security patterns are flagged when scanning staged git diffs for commits?

Scanning staged git diffs flags likely secrets, shell and command injection patterns, eval or exec usage, unsafe deserialization, and basic SQL injection formatting risks.

Does the independent reviewer use JSON-only enforcement for code review verdicts?

Yes, the independent reviewer enforces a fail-closed JSON-only verdict on the staged diff, ensuring structured, machine-readable pass or fail decisions before committing changes.