receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill receiving-code-review-wangx7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/wangx7/skills-collection/tree/main/superpowers-main/skills/receiving-code-review
Command: npx skills add https://github.com/wangx7/skills-collection --skill receiving-code-review-wangx7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common pitfalls of mishandling code review feedback: performative agreement to avoid social discomfort, or blind implementation of unverified suggestions that lead to bugs, regressions, and wasted development effort.

Core Features & Use Cases

  • Structured Response Workflow: A 6-step process to read, understand, verify, evaluate, and respond to feedback before implementing any changes.
  • Scenario-Specific Guardrails: Tailored rules for feedback from internal collaborators, external reviewers, and GitHub pull request inline comments, including YAGNI checks and conflict resolution with prior architectural decisions.
  • Use Case: When an external reviewer suggests adding an unused metrics tracking endpoint, this Skill guides you to grep the codebase for actual usage, push back with YAGNI reasoning if it's unused, instead of implementing unnecessary code.

Quick Start

Use the receiving-code-review skill to respond to the code review feedback on your current pull request, verifying each suggestion against the codebase 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
Implementing unverified code review feedback causes regressions because it bypasses technical evaluation. Blindly accepting suggestions without checking codebase usage or enforcing YAGNI principles leads to bugs, unnecessary code, and wasted development effort.

Yes, you can evaluate GitHub pull request inline comments using a 6-step structured workflow. This process ensures you read, understand, verify, evaluate, and respond to feedback technically before making any code modifications, preventing regressions.

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

The best way to push back on pull request comments is to apply YAGNI principles. Verify the suggested code modifications against actual codebase usage, and reject unnecessary additions like unused endpoints with technical reasoning instead of empty agreement.

How do I respond to external reviewer suggestions that conflict with my architecture?

To respond to external reviewer suggestions conflicting with your architecture, apply scenario-specific guardrails. Verify the technical merit of the feedback, evaluate it against prior architectural decisions, and push back with verified technical reasoning.

Can I use a structured workflow to evaluate GitHub pull request inline comments?

Yes, you can evaluate GitHub pull request inline comments using a 6-step structured workflow. This process ensures you read, understand, verify, evaluate, and respond to feedback technically before making any code modifications, preventing regressions.

Why does implementing unverified code review feedback cause regressions?

Implementing unverified code review feedback causes regressions because it bypasses technical evaluation. Blindly accepting suggestions without checking codebase usage or enforcing YAGNI principles leads to bugs, unnecessary code, and wasted development effort.