requesting-code-review

Scan code for security vulnerabilities and regressions before git commit.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Signmanal/VIGIL --skill requesting-code-review-signmanal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Signmanal/VIGIL/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/Signmanal/VIGIL --skill requesting-code-review-signmanal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers frequently miss critical code defects, security vulnerabilities, and quality regressions in their own work before committing, leading to costly post-commit fixes, security incidents, and broken production builds. Manual code review is time-consuming, inconsistent, and often fails to catch subtle issues that automated tools and fresh reviewer context can identify immediately.

Core Features & Use Cases

  • Automated Static Security Scanning: Detects common vulnerabilities like hardcoded secrets, shell injection, SQL injection, and unsafe deserialization in added code lines before commit.
  • Baseline-Aware Quality Gates: Only flags new test failures or lint errors introduced by changes, ignoring pre-existing issues in the codebase to avoid false positives.
  • Independent Subagent Review + Auto-Fix: Dispatches a separate, context-isolated reviewer agent to catch logic errors and security issues the implementer missed, with an automated fix loop that resolves reported problems in up to two retry cycles.
  • Use Case: A developer finishing a new payment processing feature can run this skill to automatically scan for security flaws, run tests to check for regressions, get an independent review, and fix any minor issues before committing, preventing vulnerable code from reaching the repository.

Quick Start

Use the requesting-code-review skill to verify your recent code changes and automatically fix any identified issues before committing them to your git repository.

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 and automated code review before a git commit?

Pre-commit code review runs automated static security scanning and an independent subagent review on your changes, applying iterative auto-fixes to identified vulnerabilities before the git commit operation.

How does baseline-aware linting prevent false positives during pre-commit verification?

Baseline-aware quality gates only flag new test failures or lint errors introduced by your current changes, ignoring pre-existing issues in the codebase to avoid false positives during pre-commit verification.

Can I automatically fix code defects and security vulnerabilities found during static analysis?

Yes, static analysis includes an automated fix loop that resolves reported code defects and security vulnerabilities in up to two retry cycles with fail-closed safety guardrails.

What types of security vulnerabilities does a pre-commit static analysis scan detect?

Static security scanning detects common vulnerabilities in added code lines, including hardcoded secrets, shell injection, SQL injection, and unsafe deserialization before they reach version control.

Does the independent subagent code review work separately from the main development context?

Independent subagent review dispatches a separate, context-isolated reviewer agent to catch logic errors and security issues the implementer missed during the code review process.

What are the limitations of automated auto-fix loops for pre-commit code review?

The automated auto-fix loop is limited to resolving reported issues in up to two retry cycles, using fail-closed safety guardrails to prevent unsafe code from passing quality gates.