superpowers-receiving-code-review

Verify and clarify code review feedback before implementing changes.

90|5|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review-christopherarter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-receiving-code-review
Source: https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-receiving-code-review
Command: npx skills add https://github.com/christopherarter/superpowers-reasonix --skill superpowers-receiving-code-review-christopherarter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies and clarifies code review feedback before any change, reducing rework and misinterpretation.

Core Features & Use Cases

  • Read, restate, and verify each feedback item against the target codebase.
  • Decide when to push back with technical reasoning or proceed with small, verifiable changes.
  • Use in PR workflows to ensure changes align with requirements, architectural decisions, and testing criteria.

Quick Start

Load a review feedback item and initiate the verification workflow before implementing any changes.

Frequently Asked Questions about superpowers-receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code review feedback before implementing changes?

To verify code review feedback, restate each item, check it against the target codebase for correctness, and clarify any unclear points before proceeding with implementation one change at a time.

What is the best way to handle unclear pull request feedback?

Handling unclear pull request feedback requires clarifying the ambiguous items first, validating the suggested changes against current codebase requirements, and then implementing small, verifiable updates with tests.

How do I process code review comments from subagents or automated tools?

Processing code review comments from subagents involves verifying each feedback item against the codebase, deciding when to push back with technical reasoning, and implementing validated changes individually with guardrails.

When should I push back on code review feedback instead of implementing it?

You should push back on code review feedback when the suggestions do not align with architectural decisions or codebase requirements, providing technical reasoning rather than proceeding with incorrect changes.

Can I use this verification workflow for human code review comments?

Yes, this verification workflow applies to code review feedback from both humans and subagents, ensuring every item is validated against the codebase before any implementation begins.

How do I implement verified code review changes without introducing regressions?

Implement verified code review changes by processing items one at a time, applying tests and guardrails to each small change, ensuring updates align with requirements and architectural decisions before deployment.