skills.rest
xhyqaq
xhyqaqCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verifies GitHub pull-request feedback before implementing code changes.

63|2|Updated Mar 29, 2026
Search Tags:#code review#pull request#YAGNI#technical verification#feedback handling#review pushback
One-click install
npx skills add https://github.com/xhyqaq/superpowers-plus --skill receiving-code-review-xhyqaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/xhyqaq/superpowers-plus/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/xhyqaq/superpowers-plus --skill receiving-code-review-xhyqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common issue of mishandling code review feedback, which often leads to broken functionality, unnecessary code bloat, or missed technical issues from unverified, performative responses or blind implementation of suggestions.

Core Features & Use Cases

  • Structured Verification Workflow: Follow a step-by-step process to read, understand, verify, and evaluate feedback before acting, avoiding rushed or incorrect changes.
  • Guardrails Against Common Mistakes: Eliminate performative agreement, blind implementation of unvetted suggestions, and partial fixes that miss related issues.
  • Context-Aware Handling: Includes specific guidance for feedback from your human partner vs. external reviewers, YAGNI checks for unnecessary "professional" features, and proper pushback techniques for technically incorrect suggestions.
  • Use Case: When a reviewer asks you to remove legacy code that supports older OS versions your product still targets, this Skill guides you to verify the compatibility requirements first instead of immediately deleting the code and breaking support for existing users.

Quick Start

Use the receiving-code-review skill to respond to the code review feedback on your latest pull request, verifying each suggestion before implementing any 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 without blindly implementing every suggestion?▼

Handle code review feedback by applying a structured verification workflow that reads, understands, verifies, and evaluates each suggestion before acting. This prevents broken functionality, unnecessary code bloat, and performative responses by adding guardrails against blind implementation of unvetted changes.

How do I push back on technically incorrect code review comments on a pull request?▼

Push back on technically incorrect code review comments using guided technical pushback and clarification request techniques. Instead of performative agreement, the workflow helps you verify compatibility requirements first, ensuring you do not break existing functionality by prematurely removing legacy code.

What is the best way to apply YAGNI validation to feature suggestions from external reviewers?▼

Apply YAGNI validation to feature suggestions by checking if requested professional features are actually necessary before implementation. This context-aware handling distinguishes feedback from internal partners versus external reviewers, preventing unnecessary code bloat from unverified additions.

How do I stop missing related issues when fixing partial code review feedback?▼

Stop missing related issues by following a step-by-step verification process that evaluates feedback comprehensively. Guardrails eliminate partial fixes by ensuring you verify the full scope of related technical issues before making any code changes.

Does this code review workflow work with inline GitHub pull request comments?▼

Yes, this code review workflow works with inline GitHub pull request comments. It applies to all code review interactions including feedback from internal human partners, external reviewers, and inline pull request comments.

When should I not implement a code review suggestion immediately?▼

You should not implement a code review suggestion immediately when it lacks technical verification or breaks compatibility. If a reviewer asks you to remove legacy code supporting older OS versions your product still targets, verify compatibility requirements first instead of blindly deleting the code.

Related Skills

Explore More Software Engineering Skills→
Luney-IndustriesLuney-Industries
4

address-pr-comments

Categorize GitHub pull request comments and generate action plans.

Official
Advanced
idoberkidoberk

receiving-code-review

Evaluate code review feedback for technical correctness before implementation.

Community
Intermediate
Sir-chawakornSir-chawakorn
33

pr-review

Automate Pull Request reviews for code quality, security, and performance.

Community
Advanced
SuperCorksSuperCorks

address-pr-comments

Fetch GitHub PR reviews via gh CLI and apply latest reviewer feedback.

Community
Advanced