requesting-code-review

Scan git diffs for security risks and run baseline-aware tests before commit.

Updated May 24, 2026

Search Tags:#code review #linting #auto-fix #pre-commit #security scan #test regression

Ready to run

npx skills add https://github.com/anxiety135790/hermes-skills --skill requesting-code-review-anxiety135790

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/requesting-code-review
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill requesting-code-review-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify your own code changes before committing so you can catch security issues, logic mistakes, and test regressions before they reach the repository.

Core Features & Use Cases

Static security scanning: Checks diffs for secrets, shell injection, unsafe eval/exec usage, dangerous deserialization, and SQL injection patterns.
Baseline-aware quality gates: Runs language-appropriate tests and linters, then compares results against the pre-change baseline so only new failures block progress.
Independent review workflow: Uses a separate reviewer agent and, if needed, an auto-fix loop to correct issues without the implementer reviewing their own work.
Use case: Before a commit or push, run this Skill on a multi-file feature change to confirm it is safe, tested, and ready to land.

Quick Start

Ask the AI to review your staged changes for security issues, test regressions, and code quality problems before you 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 staged git changes before committing?▼

A pre-commit security scan checks staged git diffs for secrets, shell injection, unsafe eval, and SQL injection patterns. This validation blocks dangerous code from reaching the repository by inspecting changes before they are committed.

How do I run tests and linting only on changed code to avoid pre-existing failures?▼

Baseline-aware test and lint execution compares results against the pre-change state, ensuring only new failures block progress. This prevents pre-existing test regressions or linting errors from stopping your pre-commit validation workflow.

Can I use an independent reviewer agent to check my code before a commit?▼

Yes, an independent reviewer agent can check your code before a commit. This pre-commit workflow uses a separate agent to review staged changes and can trigger an auto-fix loop, ensuring the implementer does not review their own work.

What is the best way to catch logic mistakes in multi-file feature changes before pushing?▼

The best way to catch logic mistakes in multi-file changes is running a pre-commit validation workflow. This process inspects git diffs, executes language-aware tests, and coordinates an independent review to confirm the feature is safe and ready to land.

What static security checks should I run before committing code?▼

Static security checks for pre-commit validation should scan diffs for secrets, shell injection, unsafe eval or exec usage, dangerous deserialization, and SQL injection patterns. These checks catch security risks in staged code before they reach the repository.

Does pre-commit code review support auto-fixing detected issues?▼

Yes, pre-commit code review supports auto-fixing detected issues. When the independent reviewer agent finds problems, an auto-fix loop can correct security risks and test regressions automatically without requiring manual intervention.