requesting-code-review

requesting-code-review is a skill for Claude Code, Codex from ChrisLamDev/hermes-core-skills. It costs 56 tokens per session (3,200 once invoked), scanned A, original, MIT.

A pre-commit check for code changes that scans the proposed changes, applies quality checks, gets a second review, and can retry fixes.

In plain words
What is it for?
Use it after implementing a feature or bug fix in a Git repository, especially when several files changed and you want an independent review before the code lands.
Why use it?
It helps catch security issues, quality problems, and missed mistakes before changes are committed, pushed, or proposed for merging.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/chrislamdev/hermes-core-skills/requesting-code-review
Any agent
npx skills add ChrisLamDev/hermes-core-skills --skill requesting-code-review
Clone the repo
git clone --depth 1 https://github.com/ChrisLamDev/hermes-core-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for requesting-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrislamdev/hermes-core-skills/requesting-code-review.svg)](https://agentmods.dev/skills/chrislamdev/hermes-core-skills/requesting-code-review)
Your own site
<a href="https://agentmods.dev/skills/chrislamdev/hermes-core-skills/requesting-code-review"><img src="https://agentmods.dev/badge/skills/chrislamdev/hermes-core-skills/requesting-code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,200 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.03200
Opus 5 $0.00028 $0.01600
Sonnet 5 $0.00011 $0.00640
Haiku 4.5 $0.00006 $0.00320

Measured 4d ago against content hash 49116a8bc8ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

requesting-code-review scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

os.system(f"ls {user_input}")
skills/requesting-code-review/SKILL.md · 400 lines

How it starts

The opening of the file, as written. The whole thing — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pre-Commit Code Verification

Automated verification pipeline before code lands. Static scans, baseline-aware quality gates, an independent reviewer subagent, and an auto-fix loop.

Core principle: No agent should verify its own work. Fresh context finds what you miss.

When to Use

  • After implementing a feature or bug fix, before git commit or git push
  • When user says "commit", "push", "ship", "done", "verify", or "review before merge"
  • After completing a task with 2+ file edits in a git repo
  • After each task in subagent-driven-development (the two-stage review)

Skip for: documentation-only changes, pure config tweaks, or when user says "skip verification".

This skill vs github-code-review: This skill verifies YOUR changes before committing. github-code-review reviews OTHER people's PRs on GitHub with inline comments.

Step 1 — Get the diff

git diff --cached

If empty, try git diff then git diff HEAD~1 HEAD.

If git diff --cached is empty but git diff shows changes, tell the user to git add <files> first. If still empty, run git status — nothing to verify.

If the diff exceeds 15,000 characters, split by file:

git diff --name-only
git diff HEAD -- specific_file.py

Step 2 — Static security scan + Threat Model

Scan added lines only. Any match is a security concern fed into Step 5.

快速 Threat Model: 先諗 30 秒像黑客咁思考:

  1. Map the trust boundaries — Untrusted data 喺邊度入嚟?HTTP request, form fields, file uploads, webhooks, third-party APIs, LLM output
  2. Name the assets — 邊啲資料值得偷或破壞?Credentials, PII, payment data, admin actions
  3. Run STRIDE over each boundary — Spoofing? Tampering? Repudiation? Info disclosure? DoS? Elevation?

Scan added lines only. Any match is a security concern fed into Step 5.

# Hardcoded secrets
git diff --cached | grep "^+" | grep -iE "(api_key|secret|password|token|passwd)\s*=\s*['\"][^'\"]{6,}['\"]"

# Shell injection
git diff --cached | grep "^+" | grep -E "os\.system\(|subprocess.*shell=True"

# Dangerous eval/exec
git diff --cached | grep "^+" | grep -E "\beval\(|\bexec\("

# Unsafe deserialization
git diff --cached | grep "^+" | grep -E "pickle\.loads?\("

# SQL injection (string formatting in queries)
git diff --cached | grep "^+" | grep -E "execute\(f\"|\.format\(.*SELECT|\.format\(.*INSERT"

Read the full file on GitHub · 400 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 400 lines · 56 tokens per session scan A 49116a8bc8ff

Subscribe to this mod's changes

requesting-code-review is a skill published in the GitHub repository ChrisLamDev/hermes-core-skills (9 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 3,200 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.