Skip to content
SkillModel-led1,444 tokens in use

receiving-code-review

Makes your coding agent verify review feedback against the codebase, ask about unclear items, push back when wrong and fix one at a time.

322,762 stars on the repository MIT Licenseobra/superpowers · skills/receiving-code-review
/plugin install superpowers@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing receiving-code-review costs

38tokens idle
1,444tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectednetworkdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure19/25
  • Examples12/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity56
  • Maintenance68
  • Community64
  • Maturity36
  • Momentum40

Receiving Code Review gives your agent a six-step response pattern: read the full feedback, restate it, check it against the codebase, evaluate it for this project, respond with a technical acknowledgment or reasoned pushback, and implement one item at a time with a test after each.

What You Get

  • A response pattern that runs from reading the feedback to implementing it
  • Source-specific handling for your own feedback and for external reviewers
  • Guidance on when and how to push back, and how to correct yourself when the pushback was wrong
  • An implementation order: blocking issues, simple fixes, then complex ones

Common Use Cases

  • Working through a pull request review with many comments
  • Evaluating suggestions from an external reviewer or bot
  • Handling a request like fix items 1 to 6 when some items are unclear

What Makes It Unique

Most review skills help produce a review. This one governs how an agent receives one. It forbids reflexive agreement, requires verification against the real code before any change, and lists concrete phrases to avoid, so each piece of feedback is evaluated before it is applied.

Under The Hood

The skill is instructions only, with no scripts to run. It shapes how the agent reasons and replies, and it sends the agent to the codebase with search and test commands to verify suggestions. For feedback left on GitHub it tells the agent to reply inside the comment thread through the gh command-line tool, which calls the GitHub API.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers