receiving-code-review

Verify code review feedback technically before implementing suggested changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically evaluated and verified before implementation, preventing the blind acceptance of potentially incorrect or unnecessary changes. It promotes rigorous verification over performative agreement.

Core Features & Use Cases

  • Technical Verification: Empowers agents to question and verify feedback against the codebase's reality.
  • Reasoned Pushback: Facilitates constructive technical disagreements when feedback is flawed.
  • Structured Implementation: Guides the agent to implement verified feedback item by item, with testing.
  • Use Case: When a reviewer suggests a change, the agent first checks if the suggestion is technically sound for the current codebase, if it breaks existing functionality, or if it violates YAGNI principles, before proceeding with implementation.

Quick Start

When receiving code review feedback, verify each item technically before implementing any suggestions.

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?

Evaluate code review feedback by verifying each suggestion against the codebase's reality, checking for technical soundness, existing functionality breaks, or YAGNI principle violations before proceeding with structured implementation.

What is the best way to handle incorrect code review suggestions?

Handle incorrect code review suggestions through reasoned pushback, facilitating constructive technical disagreements when feedback is flawed rather than blindly accepting potentially unnecessary changes.

How do I implement verified code review feedback item by item?

Implement verified code review feedback through a structured process, applying each technically evaluated item individually with corresponding testing to ensure correctness and adherence to project context.

When should I push back on code review comments?

Push back on code review comments when feedback is technically flawed, violates YAGNI principles, breaks existing functionality, or lacks clarity after verification against the current codebase.

How do I clarify unclear code review feedback?

Clarify unclear code review feedback by requesting additional details from the reviewer, then applying skepticism and careful checking to external reviewer suggestions before any implementation.

Why does blind acceptance of code review feedback cause problems?

Blind acceptance of code review feedback causes problems by skipping technical verification, leading to potentially incorrect changes, broken functionality, and performative agreement rather than rigorous technical evaluation.