What is receiving-code-review?

A procedure for handling code-review feedback by understanding and technically checking each suggestion before changing the code.

Evaluating review comments, asking for clarification, implementing valid fixes one at a time, adding regression tests when needed, and explaining justified pushback.

It prevents blindly applying feedback that may be unclear, incorrect, or unsuitable for the codebase.

receiving-code-review — Skill for Claude Code and Codex by coctostan

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 receiving-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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/receiving-code-review/github.svg)](https://agentmods.dev/skills/coctostan/pi-superpowers-plus/receiving-code-review)

Your own site

<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/receiving-code-review"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/receiving-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/coctostan/pi-superpowers-plus/receiving-code-review"><img src="https://agentmods.dev/badge/skills/coctostan/pi-superpowers-plus/receiving-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,413 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 84% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.01413
Opus 5.5	$0.00015	$0.00565
Sonnet 5.5	$0.00008	$0.00283
Haiku 4.5	$0.00004	$0.00141

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

Security

Grade A, and why

receiving-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

84% identical to receiving-code-review — 51 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/receiving-code-review/SKILL.md · 197 lines

How it starts

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

Related skills: Verify each fix with /skill:verification-before-completion. Use /skill:test-driven-development for regression tests.

Code Review Reception

Overview

Code review requires technical evaluation, not emotional performance.

Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

The Response Pattern

WHEN receiving code review feedback:

1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each

How to Respond

Never performative:

❌ "You're absolutely right!" / "Great point!" / "Thanks for catching that!"
❌ "Let me implement that now" (before verification)

Instead:

✅ "Fixed. [Brief description of what changed]"
✅ "Good catch - [specific issue]. Fixed in [location]."
✅ Just fix it silently — the code shows you heard the feedback
✅ Push back with technical reasoning if wrong
✅ Ask clarifying questions if unclear

Handling Unclear Feedback

IF any item is unclear:
  STOP - do not implement anything yet
  ASK for clarification on unclear items

WHY: Items may be related. Partial understanding = wrong implementation.

Example:

your human partner: "Fix 1-6"
You understand 1,2,3,6. Unclear on 4,5.

❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later
✅ RIGHT: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding."

Source-Specific Handling

From your human partner

Trusted - implement after understanding
Still ask if scope unclear
No performative agreement
Skip to action or technical acknowledgment

From External Reviewers

BEFORE implementing:
  1. Check: Technically correct for THIS codebase?
  2. Check: Breaks existing functionality?
  3. Check: Reason for current implementation?
  4. Check: Works on all platforms/versions?
  5. Check: Does reviewer understand full context?

IF suggestion seems wrong:
  Push back with technical reasoning

IF can't easily verify:
  Say so: "I can't verify this without [X]. Should I [investigate/ask/proceed]?"

IF conflicts with your human partner's prior decisions:
  Stop and discuss with your human partner first

Read the full file on GitHub · 197 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.

1mo ago First seen · 197 lines · 38 tokens per session scan A b56306640062

Subscribe to this mod's changes

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

Code review ai-tools pi pi-extension

peer-agent

Manage resident peer agents: long-running monitors that live inside the pi session, tick on minute intervals, watch the main agent's work, and push findings back mid-turn. Use when the user asks to launch/stop/ask a peer, watcher, monitor, observer, sentinel, or auditor; wants standing review, drift/scope watching…

panbergco/pi-peer-agent · 124 tokens

tuicr

Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, tmux, Zellij, or Herdr when a user needs an interactive review pane.

agavra/tuicr · 50 tokens

liveagent-code-review

Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.

Stack-Cairn/LiveAgent · 54 tokens

receiving-code-review