Agent skill

Superpowers Receiving Code Review

by christopherarter in christopherarter/superpowers-reasonix

Got review feedback?. An agent skill from christopherarter/superpowers-reasonix.

MITAuto-check passedDevelopment

Install Superpowers Receiving Code Review

skills CLI

$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install christopherarter/superpowers-reasonix superpowers-receiving-code-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/superpowers-receiving-code-review .claude/skills/superpowers-receiving-code-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "superpowers-receiving-code-review" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review into .claude/skills/superpowers-receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-receiving-code-review", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install christopherarter/superpowers-reasonix superpowers-receiving-code-review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/superpowers-receiving-code-review .agents/skills/superpowers-receiving-code-review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "superpowers-receiving-code-review" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review into .agents/skills/superpowers-receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-receiving-code-review", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install christopherarter/superpowers-reasonix superpowers-receiving-code-review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/superpowers-receiving-code-review .cursor/skills/superpowers-receiving-code-review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "superpowers-receiving-code-review" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review into .cursor/skills/superpowers-receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-receiving-code-review", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/christopherarter/superpowers-reasonix.git --path skills/superpowers-receiving-code-review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install christopherarter/superpowers-reasonix superpowers-receiving-code-review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/superpowers-receiving-code-review .gemini/skills/superpowers-receiving-code-review && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "superpowers-receiving-code-review" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review into .gemini/skills/superpowers-receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-receiving-code-review", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install christopherarter/superpowers-reasonix superpowers-receiving-code-review

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/superpowers-receiving-code-review .github/skills/superpowers-receiving-code-review && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "superpowers-receiving-code-review" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review into .github/skills/superpowers-receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-receiving-code-review", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install christopherarter/superpowers-reasonix superpowers-receiving-code-review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/superpowers-receiving-code-review .opencode/skills/superpowers-receiving-code-review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "superpowers-receiving-code-review" agent skill from https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review into .opencode/skills/superpowers-receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-receiving-code-review", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: superpowers-receiving-code-review
GitHub stars: 102
Token cost: ~1.2k tokens
SKILL.md length: 316 words
Files: 1
Skills in repo: 11
Repo updated: Aug 20, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Got review feedback?. An agent skill from christopherarter/superpowers-reasonix.

Tasks that involve Code review
SKILL.md covers Overview, The Response Pattern, Forbidden Responses and Handling Unclear Feedback, plus 9 more sections
Calls gh

What it does

Superpowers Receiving Code Review is an agent skill from christopherarter/superpowers-reasonix. Got review feedback? Load BEFORE changing anything — verify each point, push back if wrong.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review. The repository describes itself as: Superpowers skill port to Reasonix coding harness. The licence is MIT.

When your agent uses it

Tasks that involve Code review

Example prompts

“/superpowers-receiving-code-review”

What it can do on your machine

Read from SKILL.md and the folder at commit d202ba4. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Superpowers Receiving Code Review loads about 1.2k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 316 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~31
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from christopherarter/superpowers-reasonix at commit d202ba4, republished under its MIT licence (© christopherarter). 316 words, ~1,216 tokens.

Download SKILL.mdSave it as .claude/skills/superpowers-receiving-code-review/SKILL.md (or your agent's skills folder).

name: superpowers-receiving-code-review
description: Got review feedback? Load BEFORE changing anything — verify each point, push back if wrong.

Code Review Reception

Overview

Code review = technical evaluation. Not emotional performance.

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

The Response Pattern

WHEN receiving code review feedback:

1. READ: Full feedback, no 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 ack or reasoned pushback
6. IMPLEMENT: One item at a time, test each

Forbidden Responses

NEVER:

"You're absolutely right!" (performative agreement)
"Great point!" / "Excellent feedback!" (performative)
"Let me implement that now" (before verification)

INSTEAD: restate technical requirement; ask clarifying questions; push back with technical reasoning if wrong; or just start working (actions > words).

Handling Unclear Feedback

IF any item unclear:
  STOP - implement nothing yet
  ASK for clarification on unclear items

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

Example:

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

❌ WRONG: Implement 1,2,3,6 now, ask 4,5 later
✅ RIGHT: "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 ack

From External Reviewers (or a reviewer subagent)

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

IF suggestion seems wrong: push back with technical reasoning
IF can't easily verify: "I can't verify this without [X]. Should I [investigate/ask/proceed]?"
IF conflicts with your human partner's prior decisions: stop and discuss first

Rule: External feedback — stay skeptical. Check carefully.

YAGNI Check for "Professional" Features

IF reviewer suggests "implementing properly":
  grep codebase for actual usage
  IF unused: "Endpoint isn't called. Remove it (YAGNI)?"
  IF used: implement properly

Implementation Order

FOR multi-item feedback:
  1. Clarify anything unclear FIRST
  2. Then implement in order:
     - Blocking issues (breaks, security)
     - Simple fixes (typos, imports)
     - Complex fixes (refactoring, logic)
  3. Test each fix individually
  4. Verify no regressions

When To Push Back

Push back when suggestion: breaks existing functionality; comes from reviewer lacking full context; violates YAGNI (unused feature); is technically incorrect for this stack; ignores legacy/compatibility reasons; conflicts with your human partner's architectural decisions.

How: technical reasoning, not defensiveness; ask specific questions; reference working tests/code; involve your human partner if architectural.

Acknowledging Correct Feedback

✅ "Fixed. [what changed]"
✅ "Good catch - [specific issue]. Fixed in [location]."
✅ [Just fix it; show it in code]

❌ "You're absolutely right!"  ❌ "Great point!"  ❌ "Thanks for catching that!"
❌ ANY gratitude expression

Why no thanks: actions speak. Just fix it — code shows you heard. Catch yourself writing "Thanks"? Delete it. State the fix.

Gracefully Correcting Your Pushback

Pushed back, but wrong:

✅ "You were right - checked [X], it does [Y]. Implementing now."
✅ "Verified, you're correct. My understanding was wrong because [reason]. Fixing."

❌ Long apology   ❌ Defending why you pushed back   ❌ Over-explaining

State correction factually. Move on.

Common Mistakes

Mistake	Fix
Performative agreement	State requirement or just act
Blind implementation	Verify against codebase first
Batch without testing	One at a time, test each
Assuming reviewer is right	Check if it breaks things
Avoiding pushback	Technical correctness > comfort
Partial implementation	Clarify all items first
Can't verify, proceed anyway	State limitation, ask for direction

GitHub Thread Replies

Replying to inline GitHub review comments? Reply in the thread (gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies), not as a top-level PR comment.

The Bottom Line

External feedback = suggestions to evaluate, not orders to follow.

Evaluate each item against the actual code before acting. Push back on what's wrong. No performative agreement. Technical rigor always.

Files

Just SKILL.md in skills/superpowers-receiving-code-review of christopherarter/superpowers-reasonix.

Open the folder on GitHubat commit d202ba4

Compare with similar skills

Superpowers Receiving Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Superpowers Receiving Code Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Superpowers Receiving Code Review this skillchristopherarter/superpowers-reasonix	102	—	~1.2k	Automated safety check: Pass	MIT	1 mo ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	yesterday
Code Review ChecklistshareAI-lab/learn-claude-code	78k	5 repos	~1.1k	Automated safety check: Pass	MIT	9 days ago
Backend Code Reviewlangflow-ai/langflow	156k	—	~3.5k	Automated safety check: Notes	MIT	today
Understand Diff AnalysisEgonex-AI/Understand-Anything	85k	1 repos	~1.4k	Automated safety check: Pass	MIT	2 days ago
Mole Bug Patternstw93/Mole	69k	—	~2k	Automated safety check: Pass	GPL-3.0	yesterday

Similar skills

PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
156k GitHub stars~3.5k tokensUpdated today
DevelopmentAuto-check: notes
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
85k GitHub starsUsed in 1 repo~1.4k tokens
DevelopmentAuto-check passed
Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
69k GitHub stars~2k tokensUpdated yesterday
DevelopmentAuto-check passed
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
158k GitHub stars~676 tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Superpowers Receiving Code Review

What does Superpowers Receiving Code Review do?

Got review feedback?. An agent skill from christopherarter/superpowers-reasonix. Superpowers Receiving Code Review is an agent skill from christopherarter/superpowers-reasonix. Got review feedback?

When should I use Superpowers Receiving Code Review?

Superpowers Receiving Code Review fits situations like: tasks that involve Code review.

How do I install Superpowers Receiving Code Review in Claude Code?

Run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a claude-code`. Or copy the skill folder (skills/superpowers-receiving-code-review in christopherarter/superpowers-reasonix) into .claude/skills/superpowers-receiving-code-review in your project. Claude Code loads it when a task matches its description.

How do I install Superpowers Receiving Code Review in Codex?

Run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a codex`. Or copy the skill folder (skills/superpowers-receiving-code-review in christopherarter/superpowers-reasonix) into .agents/skills/superpowers-receiving-code-review in your project. Codex loads it when a task matches its description.

Can I use Superpowers Receiving Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superpowers-receiving-code-review, .gemini/skills/superpowers-receiving-code-review, .github/skills/superpowers-receiving-code-review and .opencode/skills/superpowers-receiving-code-review in your project.

What does Superpowers Receiving Code Review need to run?

Going by SKILL.md and its folder, Superpowers Receiving Code Review needs the command-line tools its instructions call (gh).

Does Superpowers Receiving Code Review access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Superpowers Receiving Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Superpowers Receiving Code Review use?

Superpowers Receiving Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Superpowers Receiving Code Review use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Superpowers Receiving Code Review?

Skills that share tags, products or a category with Superpowers Receiving Code Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 156k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Superpowers Receiving Code Review?

christopherarter (a GitHub user) maintains it in christopherarter/superpowers-reasonix, which has 102 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 20, 2026.

Source: christopherarter/superpowers-reasonix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Superpowers Receiving Code Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Code Review Reception

Overview

The Response Pattern

Forbidden Responses

Handling Unclear Feedback

Source-Specific Handling

From your human partner

From External Reviewers (or a reviewer subagent)

YAGNI Check for "Professional" Features

Implementation Order

When To Push Back

Acknowledging Correct Feedback

Gracefully Correcting Your Pushback

Common Mistakes

GitHub Thread Replies

The Bottom Line

Files

Compare with similar skills

Similar skills

More from christopherarter/superpowers-reasonix

Related

Questions about Superpowers Receiving Code Review