requesting-code-review

requesting-code-review is a skill for Claude Code, Codex from coctostan/pi-superpowers-plus. It costs 22 tokens per session (721 once invoked), scanned A, a copy of requesting-code-review, MIT.

A workflow for asking another agent to review completed code before a major merge or after an important task. It requires verification first, meaning the relevant tests must pass.

In plain words
What is it for?
Use it after implementation, during subagent-based work, before merging, when stuck, or after fixing a complicated bug.
Why use it?
A separate review can catch defects or missed requirements before they spread into later work or the main code branch.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; positional $N argument.

Good fit Use it after implementation, during subagent-based work, before merging, when stuck, or after fixing a complicated bug.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/coctostan/pi-superpowers-plus/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 coctostan/pi-superpowers-plus --skill requesting-code-review
Clone the repo
git clone --depth 1 https://github.com/coctostan/pi-superpowers-plus

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/coctostan/pi-superpowers-plus/requesting-code-review/github.svg)](https://agentmods.dev/skills/coctostan/pi-superpowers-plus/requesting-code-review)
Your own site
<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/requesting-code-review"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/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/coctostan/pi-superpowers-plus/requesting-code-review"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/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 721 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 73% 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.00721
Opus 5.5 $0.00009 $0.00288
Sonnet 5.5 $0.00004 $0.00144
Haiku 4.5 $0.00002 $0.00072

Measured 1mo ago against content hash c3b2425e0d01, 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 1mo 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

73% identical to requesting-code-review — 50 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.

skills/requesting-code-review/SKILL.md · 116 lines

How it starts

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

Related skills: Before requesting review, verify with /skill:verification-before-completion that tests pass.

Requesting Code Review

Dispatch a subagent with the code-reviewer prompt template to catch issues before they cascade.

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:

Fill the template at code-reviewer.md in this skill directory, then dispatch a subagent with it.

How to dispatch:

Use the subagent tool with the code-reviewer template filled in:

subagent({ agent: "code-reviewer", task: "... filled template ..." })

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 code-reviewer subagent]
  WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
  PLAN_OR_REQUIREMENTS: Task 2 from docs/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 · 116 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. 1mo ago First seen · 116 lines · 22 tokens per session scan A c3b2425e0d01

Subscribe to this mod's changes

requesting-code-review is a skill published in the GitHub repository coctostan/pi-superpowers-plus (106 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 721 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 73% identical to requesting-code-review, differing in 50 lines, and is treated as a copy.