superpowers-receiving-code-review

Verify code review feedback against the codebase before implementing changes.

2|1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/aldoborrero/agent-kit --skill superpowers-receiving-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-receiving-code-review
Source: https://github.com/aldoborrero/agent-kit/tree/main/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/aldoborrero/agent-kit --skill superpowers-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

What problem does it solve?

Code reviews can be emotionally driven or technically vague. This workflow enforces a rigorous, methodical approach to interpreting feedback, verifying requirements, and preventing blind compliance.

Core Features & Use Cases

  • Restate and clarify feedback to ensure understanding.
  • Verify feedback against the codebase, tests, and project standards.
  • Push back with technical reasoning when feedback is unclear or incorrect.
  • Implement changes one item at a time with targeted validation.

Quick Start

When you receive code review feedback, restate the requirement, verify it against the repository, and push back with technical justification before implementing.

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 against my codebase before implementing changes?

Verify code review feedback by restating the requirements, checking for conflicts against the codebase, and validating the technical accuracy of the suggestions before writing any code.

What should I do when code review feedback is technically vague or unclear?

When code review feedback is unclear, restate the requirement to ensure understanding and push back with reasoned technical arguments if the suggestion remains technically questionable or incorrect.

How do I push back on code review comments with technical reasoning?

Push back on code review comments by applying a structured decision process that verifies the feedback against project standards and provides reasoned technical arguments for why the suggestion is incorrect.

What is the best way to implement code review changes without introducing regressions?

Implement code review changes without regressions by executing updates one item at a time, testing each update individually to ensure no regressions occur during the targeted validation process.

When should I avoid blind implementation of code review feedback?

Avoid blind implementation of code review feedback whenever suggestions seem technically questionable, enforcing technical rigor and verification instead of performative agreement with the reviewer.

Does navigating code review feedback require checking project standards and tests?

Navigating code review feedback requires checking project standards and tests to verify the technical accuracy of the incoming suggestions against the existing codebase before proceeding with implementation.