skills.rest
zengbaocheng
zengbaochengCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Verify git diffs with security scans, baseline tests, and independent review.

Updated May 23, 2026
Search Tags:#automation#git#security#pre-commit#lint#code-review
One-click install
npx skills add https://github.com/zengbaocheng/hermes-tech-hub --skill requesting-code-review-zengbaocheng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/zengbaocheng/hermes-tech-hub/tree/main/software-development/requesting-code-review
Command: npx skills add https://github.com/zengbaocheng/hermes-tech-hub --skill requesting-code-review-zengbaocheng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated verification of code changes before landing, including security scans, baseline tests, and independent reviewer checks, to prevent defects from reaching main branches.

Core Features & Use Cases

  • Static security scan of diffs and inputs to identify secrets, risky patterns, and unsafe constructs.
  • Baseline tests and linting to ensure new changes meet project quality gates before commit.
  • Independent reviewer subagent workflow that provides a structured code-review pass for GitHub PRs or local commits.
  • Quick manual self-review: verify changes align with intent and adhere to safety requirements.

Quick Start

Run the pre-commit verification workflow before committing changes to ensure code quality and security gates are satisfied.

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 pre-commit security scan on my git diff to detect hardcoded secrets?▼

To run a pre-commit security scan on your git diff, the Skill applies a structured pipeline that statically analyzes changes to detect hardcoded secrets, risky patterns, and unsafe constructs like eval usage before committing.

What is the best way to automate code review and linting before changes reach the main branch?▼

The best way to automate code review before changes reach the main branch is using a pre-commit verification pipeline that runs baseline tests, linting, and an independent reviewer subagent workflow to prevent defects.

Can I use pre-commit verification for local commits or does it only support GitHub PRs?▼

Pre-commit verification supports both local commits and GitHub PRs, utilizing an independent reviewer subagent workflow that provides a structured code-review pass for either scenario to ensure safe, auditable changes.

Does the pre-commit pipeline check for unsafe data handling and eval usage in static analysis?▼

Yes, the pre-commit pipeline includes static analysis that supports the detection of unsafe data handling, hardcoded secrets, and risky patterns like eval and exec usage within your git diffs.

How do I perform a quick manual self-review to verify my code changes align with intent?▼

To perform a quick manual self-review, you can use the verification workflow to verify that your changes align with intent and adhere to safety requirements before running the full CI-like checks.

Related Skills

Explore More Software Engineering Skills→
john-data-chenjohn-data-chen
2

requesting-code-review

Automate pre-commit code verification with static security scans, linting, and reviewer subagent workflows.

Community
Advanced
whilpwhilp
9

gh-workflow

Trigger and monitor GitHub Actions workflows via gh CLI.

Community
Advanced
TECHKNOWMAD-LABSTECHKNOWMAD-LABS

security-audit

Scan code repositories for vulnerabilities and leaked secrets using static analysis tools.

Official
Advanced
rnbenrnben

requesting-code-review

Automates pre-commit verification with security scans, baseline tests, and an auto-fix loop.

Community
Advanced