requesting-code-review

requesting-code-review is a skill for Claude Code, Codex from chinkan/RustFox. It costs 22 tokens per session (685 once invoked), scanned A, a copy of requesting-code-review, MIT.

A review step that sends completed work to a separate code reviewer for an independent check against the requirements.

In plain words
What is it for?
Use it after a task, major feature, difficult bug fix, or before merging code. It compares a starting commit with the completed work.
Why use it?
It can catch defects, missed requirements, and important issues before they spread or reach a shared branch.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; positional $N argument; installed under .agents/ (shared by several agents).

Good fit Use it after a task, major feature, difficult bug fix, or before merging code. It compares a starting commit with the completed work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chinkan/rustfox/requesting-code-review
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.

Any agent
npx skills add chinkan/RustFox --skill requesting-code-review
Clone the repo
git clone --depth 1 https://github.com/chinkan/RustFox

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/chinkan/rustfox/requesting-code-review/github.svg)](https://agentmods.dev/skills/chinkan/rustfox/requesting-code-review)
Your own site
<a href="https://agentmods.dev/skills/chinkan/rustfox/requesting-code-review"><img src="https://agentmods.dev/badge/skills/chinkan/rustfox/requesting-code-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for requesting-code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/chinkan/rustfox/requesting-code-review"><img src="https://agentmods.dev/badge/skills/chinkan/rustfox/requesting-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 685 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 83% copy Near-identical to another mod 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.1 $0.00022 $0.00685
Opus 5.5 $0.00009 $0.00274
Sonnet 5.5 $0.00004 $0.00137
Haiku 4.5 $0.00002 $0.00068

Measured 2mo ago against content hash a5ff68586ccf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

requesting-code-review scanned grade A with 0 findings 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

83% identical to requesting-code-review — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/requesting-code-review/SKILL.md · 106 lines

How it starts

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

Requesting Code Review

Dispatch superpowers:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.

Core principle: Review early, review often.

When to Request Review

Mandatory:

  • After each task in subagent-driven development
  • After completing major feature
  • Before merge to main

Optional but valuable:

  • When stuck (fresh perspective)
  • Before refactoring (baseline check)
  • After fixing complex bug

How to Request

1. Get git SHAs:

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
HEAD_SHA=$(git rev-parse HEAD)

2. Dispatch code-reviewer subagent:

Use Task tool with superpowers:code-reviewer type, fill template at code-reviewer.md

Placeholders:

  • {WHAT_WAS_IMPLEMENTED} - What you just built
  • {PLAN_OR_REQUIREMENTS} - What it should do
  • {BASE_SHA} - Starting commit
  • {HEAD_SHA} - Ending commit
  • {DESCRIPTION} - Brief summary

3. Act on feedback:

  • Fix Critical issues immediately
  • Fix Important issues before proceeding
  • Note Minor issues for later
  • Push back if reviewer is wrong (with reasoning)

Example

[Just completed Task 2: Add verification function]

You: Let me request code review before proceeding.

BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)

[Dispatch superpowers:code-reviewer subagent]
  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
  PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661
  DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types

[Subagent returns]:
  Strengths: Clean architecture, real tests
  Issues:
    Important: Missing progress indicators
    Minor: Magic number (100) for reporting interval
  Assessment: Ready to proceed

You: [Fix progress indicators]
[Continue to Task 3]

Read the full file on GitHub · 106 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 106 lines · 22 tokens per session scan A a5ff68586ccf

Subscribe to this mod's changes

requesting-code-review is a skill published in the GitHub repository chinkan/RustFox (11 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 685 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to requesting-code-review, differing in 38 lines, and is treated as a copy.

Related

Other skills, from other repositories

control-center-review

Review one captured Control Center build before runtime activation.

openonion/connectonion · 14 tokens

review-pr

Review GitHub pull requests. Use when user says "review PR", "review pull request", or "/review-pr".

openonion/connectonion · 27 tokens

spawn-reviewers

Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves CODEINTELALLOWED and CODEINTELREQUIREROOTARG, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified…

closedloop-ai/claude-plugins · 191 tokens

workflow-code-review

Run a worker-backed code review using its bundled review lenses: approach correctness, architecture ownership, correctness, guardrails, validation, compatibility, and security. Use when asked to review a PR, branch, diff, or uncommitted changes with workflow-level rigor.

closedloop-ai/claude-plugins · 56 tokens

present-local

Render the operator-facing local-mode code review results at stage29present. Covers BLOCKING/HIGH/MEDIUM section templates, Justified Findings (PLN-721), Dismissed Findings (PLN-722), Verifier Stats footer (PLN-773), operator-flag descriptions, override precedence rule for stage22b, Validation Summary, and final…

closedloop-ai/claude-plugins · 136 tokens

review-this-branch

Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.

no-human-ai/no_human · 53 tokens