receiving-code-review

Evaluate and respond to code review feedback with technical verification.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ucirello/sgai --skill receiving-code-review-ucirello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ucirello/sgai/tree/main/cmd/sgai/skel/.sgai/skills/receiving-code-review
Command: npx skills add https://github.com/ucirello/sgai --skill receiving-code-review-ucirello

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common issue of blindly accepting code review feedback, which can lead to incorrect implementations, wasted effort, and technical debt. It promotes a rigorous, verification-first approach to code review responses.

Core Features & Use Cases

  • Technical Verification: Empowers developers to technically evaluate feedback against the codebase's reality before implementation.
  • Reasoned Pushback: Provides a framework for constructively challenging feedback that is unclear, incorrect, or not aligned with project goals.
  • Prioritized Implementation: Guides the order of implementation for multiple feedback items to ensure efficiency and correctness.
  • Use Case: A reviewer suggests a change. Instead of immediately coding it, this Skill prompts you to verify its technical soundness, check for regressions, and ensure it aligns with the project's architecture, pushing back with data if necessary.

Quick Start

Use the receiving-code-review skill to evaluate feedback from an external reviewer 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 verify code review feedback before implementing changes?

Verify code review feedback by technically evaluating it against the codebase reality, checking for regressions, and ensuring alignment with project architecture before writing any code.

What is the best way to push back on incorrect code review comments?

Push back on incorrect code review comments by using a reasoned framework that challenges unclear or incorrect feedback with technical data rather than performative agreement.

How do I prioritize implementation order for multiple code review items?

Prioritize code review implementation order by evaluating each feedback item's technical soundness, checking YAGNI principles, and sequencing changes to ensure development efficiency and correctness.

When should I distinguish between feedback from human partners and external reviewers?

Distinguish between feedback from human partners and external reviewers when receiving code review comments to apply the appropriate level of technical verification and reasoned pushback for each source.

Why does blindly accepting code review feedback cause technical debt?

Blindly accepting code review feedback causes technical debt because it bypasses technical verification, leading to incorrect implementations, wasted development effort, and misaligned project architecture.

Do I need to check YAGNI principles when responding to code review feedback?

Check YAGNI principles when responding to code review feedback to ensure suggested changes are technically necessary and avoid implementing unnecessary features that complicate the codebase.