receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

70|6|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/earchibald/vsc-superpowers --skill receiving-code-review-earchibald
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/earchibald/vsc-superpowers/tree/main/.agents/skills/receive-review
Command: npx skills add https://github.com/earchibald/vsc-superpowers --skill receiving-code-review-earchibald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback can be unclear or risky to implement without technical verification. This skill enforces a disciplined process to verify requirements against the codebase before modifying code.

Core Features & Use Cases

  • READ: Complete feedback without reacting
  • UNDERSTAND: Restate requirement in own words (or ask)
  • VERIFY: Check against codebase reality
  • EVALUATE: Technically sound for THIS codebase?
  • RESPOND: Technical acknowledgment or reasoned pushback
  • IMPLEMENT: One item at a time, test each

Handling Unclear Feedback: If any item is unclear, STOP - do not implement anything yet and ASK for clarification on unclear items.

Source-Specific Handling: From human partner - Trusted, Still ask if scope unclear, No performative agreement, Skip to action or technical acknowledgment. From External Reviewers - Push back with technical reasoning if seems wrong; If can't verify, say so and ask for direction.

Quick Start

Read the feedback, restate the requirement, verify against the codebase, then respond with technical reasoning before implementing.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle conflicting code-review feedback on a pull request?

Handle conflicting code-review feedback by applying a stepwise verification pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. You must check the conflicting suggestions against codebase reality and document technical reasoning before implementing any changes.

What is the best way to verify risky code-review comments before making changes?

The best way to verify risky code-review comments is to evaluate technical soundness for your specific codebase before acting. You restating the requirement, verifying against the codebase, and providing technical acknowledgment or reasoned pushback ensures changes are safe.

How should I respond to unclear code-review feedback?

When receiving unclear code-review feedback, you should stop and ask for clarification immediately. Do not implement anything until unclear items are resolved, ensuring you fully understand the requirement before modifying code.

When should I push back on external reviewer feedback?

You should push back on external reviewer feedback with technical reasoning if the suggestion seems wrong for your codebase. If you cannot verify the technical merit of the feedback, explicitly state your uncertainty and ask for direction.

How do I implement multiple code-review changes safely?

Implement multiple code-review changes safely by processing one item at a time and testing each modification individually. This containment strategy prevents cascading failures and ensures each verified requirement is validated independently.