receiving-code-review

Receiving Code Review

Receiving Code Review is an agent skill from Superpowers: your agent checks review feedback against the code before acting, pushes back with reasons when it is wrong, and skips the flattery.

Checked by CookiesForAI on : license and last change of the skill re-read from GitHub.

Written by

Install Receiving Code Review

Install only this skill with the skills CLI

Terminal
npx skills add obra/superpowers --skill receiving-code-review

Or, in Claude Code, install the whole Superpowers plugin from Anthropic's official marketplace

Agent chat
/plugin install superpowers@claude-plugins-official

Or paste this into your coding agent: Install the agent skill receiving-code-review from github.com/obra/superpowers. Checked by CookiesForAI on : license and last change of the skill re-read from GitHub. A skill can include scripts that run on your computer, so read its source first.

What Receiving Code Review does

Receiving Code Review is one of the skills in Superpowers, Jesse Vincent's open-source method for AI coding agents. It loads when the agent receives code review feedback, before it implements any suggestion, and matters most when the feedback is unclear or looks technically wrong. The agent reads all of it, restates each point or asks about it, checks it against the actual codebase, and only then responds and implements, one item at a time with a test for each.

Receiving Code Review bans performative replies such as "You're absolutely right" or "Great point", and any thanks: the agent states the fix or simply makes it. If some items are unclear, it asks about them before implementing any, since items may be related. Feedback from you is trusted once understood. Suggestions from outside reviewers are checked first: whether they break something, whether the current code has a reason, and whether the reviewer has the full context.

Under Receiving Code Review, when a reviewer asks for something to be implemented "properly", the agent searches the codebase for real usage and suggests removing the code if nothing calls it (YAGNI). It pushes back with technical reasoning when a suggestion is wrong for this stack, and stops to discuss with you when feedback conflicts with your earlier decisions. Fixes go in a set order: blocking issues, then simple fixes, then complex ones. On GitHub it replies inside the review comment thread.

When to use Receiving Code Review

  • Your agent agrees with every review comment and changes code without checking it.
  • You are passing an outside reviewer's comments on a pull request to your agent.
  • You have review items that are unclear and want the agent to ask before it implements the rest.

When to pick something else

  • You want a review of your own changes: use Requesting Code Review.

Which agents Receiving Code Review works in

Jesse Vincent documents Receiving Code Review for Claude Code, Codex (app and CLI), Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Antigravity, Devin CLI, Factory Droid, Grok Build CLI, Kimi Code, Pi, Qwen Code, Hermes Agent, Muse. The open skills CLI also installs it into 78 agents, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode (we listed it with the CLI on ). See where each agent looks for skills.

Superpowers is written in Claude Code's vocabulary (subagent dispatch, todos, the Skill tool) and ships tool mappings for Codex, Gemini CLI, Pi, Antigravity, Hermes Agent and Muse. Installed as the full plugin, a session-start hook loads Using Superpowers so the agent reaches for skills on its own; one skill installed with the skills CLI gets no hook and may point to sibling skills you do not have.

Receiving Code Review license

Receiving Code Review is published under MIT.

More from Jesse Vincent

Lists that include receiving-code-review