receiving-code-review

Evaluate code review feedback against codebase reality before implementation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Sungmaster/Sung --skill receiving-code-review-sungmaster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Sungmaster/Sung/tree/main/.claude/plugins/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/Sungmaster/Sung --skill receiving-code-review-sungmaster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative agreement and blind implementation during code reviews, ensuring that feedback is technically verified and aligned with project requirements before any changes are made.

Core Features & Use Cases

  • Verification Workflow: Provides a structured, step-by-step process to evaluate feedback against codebase reality.
  • Pushback Protocol: Offers clear guidelines on when and how to technically challenge suggestions that violate YAGNI or architectural decisions.
  • Use Case: When a reviewer suggests a complex refactor for an unused feature, this skill guides you to verify usage via grep and push back with technical reasoning rather than blindly implementing.

Quick Start

Activate the receiving-code-review skill to process the latest pull request feedback by following the verification and response pattern defined in the documentation.

Frequently Asked Questions about receiving-code-review

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

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

Evaluating code review feedback requires a verification workflow to check suggestions against codebase reality and project requirements before integration. This prevents performative agreement by prioritizing technical correctness and architectural alignment.

What is the best way to respond to pull request comments suggesting unnecessary refactoring?

Responding to pull request comments suggesting unnecessary refactoring involves applying a pushback protocol to technically challenge suggestions that violate YAGNI. You provide technical reasoning verified against the codebase rather than blindly implementing changes.

When should I push back on peer feedback during a code review?

You should push back on peer feedback during a code review when suggestions violate YAGNI or conflict with established architectural decisions. This ensures technical rigor and engineering standards override performative agreement.

How do I verify if a reviewer's suggestion for a complex refactor is actually needed?

To verify if a reviewer's suggestion for a complex refactor is needed, you systematically check actual feature usage via grep and evaluate it against architectural decisions. This technical verification ensures you only implement necessary software quality improvements.

Does this code review verification workflow require any specific development environment setup?

This code review verification workflow requires no specific development environment setup or external dependencies. It standardizes your evaluation process directly within existing software development workflows to ensure technical correctness.