receiving-code-review

Verify code review feedback through a six-step process before implementation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/astrosteveo/marketplace --skill receiving-code-review-astrosteveo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/astrosteveo/marketplace/tree/main/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/astrosteveo/marketplace --skill receiving-code-review-astrosteveo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Guidance to read, understand, verify, evaluate, respond, and implement feedback.
  • Helps push back with technical reasoning when suggestions are unclear or wrong
  • Use Case: When code review comments are vague or conflicting and require clarification before changes.

Quick Start

Run the six-step process on feedback: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT. Start with clarifying questions for unclear items before making changes.

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 code review feedback that seems technically questionable?▼

Handle code review feedback by applying a structured verification process before implementation, ensuring technical rigor takes priority over performative agreement or blind changes.

What is the best way to push back on unclear pull request comments?▼

Push back on unclear pull request comments by asking clarifying questions and providing technical reasoning rather than blindly implementing suggestions that lack clear justification.

How do I process conflicting code review comments before making changes?▼

Process conflicting code review comments through a six-step sequence: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT, starting with clarification for vague items.

When should I verify code review suggestions instead of implementing them directly?▼

Verify code review suggestions when feedback seems unclear or technically questionable, requiring rigorous evaluation of the technical merit before modifying any pull request code.

How do I respond to vague code review feedback on my pull request?▼

Respond to vague code review feedback by first reading and attempting to understand the comment, then verifying its technical validity before evaluating and responding with clarifying questions.