skills.rest
droxey
droxeyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Convert code review feedback into a verification-first implementation workflow.

1|Updated Apr 9, 2026
Search Tags:#testing#code review#implementation planning#YAGNI#github#verification#technical pushback
One-click install
npx skills add https://github.com/droxey/skills --skill receiving-code-review-droxey
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/droxey/skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/droxey/skills --skill receiving-code-review-droxey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents incorrect, risky, or premature changes by turning incoming code review feedback into a technically verified plan of action.

Core Features & Use Cases

  • Technical Reception Protocol: Read fully, restate requirements, and verify against codebase reality before changing anything.
  • Clear Communication & Pushback: Respond with technical acknowledgment or reasoned objections when suggestions are unclear, incorrect, or conflict with prior decisions.
  • Controlled Implementation Order: Clarify unclear items first, then implement item-by-item with targeted testing and regression checks, including a YAGNI check for “proper” professional features.

Quick Start

Use the receiving-code-review skill whenever you receive PR or inline code review feedback that might be unclear, technically questionable, or conflict with your current understanding.

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 unclear code review feedback on a GitHub PR?▼

Handle unclear GitHub PR feedback by restating the requirements and verifying them against the codebase reality before implementing any changes. This verification-first workflow ensures you clarify ambiguous suggestions before taking action, preventing incorrect modifications.

What is the best way to push back on code review suggestions that violate YAGNI?▼

The best way to push back on YAGNI violations is to respond with reasoned technical objections rather than performative gratitude or blind agreement. Evaluate the suggestion technically and explicitly state why the proposed feature is premature.

How do I safely implement multiple changes requested in a code review?▼

Safely implement multiple code review changes by clarifying unclear items first, then proceeding item-by-item with targeted testing and regression checks. This controlled implementation order ensures each modification is verified independently for correctness.

When should I verify code review feedback before implementing it?▼

You should verify code review feedback before implementation whenever you receive multi-item PR comments, externally suggested changes, or recommendations that conflict with prior architectural decisions to prevent risky or premature codebase modifications.

Can I use this workflow for code review comments that conflict with prior decisions?▼

Yes, you can use this workflow for conflicting review comments by enforcing technical evaluation and reasoned pushback. It requires you to verify the feedback against existing decisions and communicate reasoned objections before altering any code.

Related Skills

Explore More Software Engineering Skills→
bonnguyenitcbonnguyenitc
19

receiving-code-review

Triage and respond to code review feedback with verification and prioritized fixes.

Community
Intermediate
greglambgreglamb
1

receiving-code-review

Evaluate code review feedback against the actual codebase before implementing changes.

Community
Intermediate
mike2oxmike2ox

my-iterate

Decompose code review feedback into actionable improvement steps.

Community
Intermediate
sangrokjungsangrokjung
1

fix

Automates lint error fixes and formatting enforcement via yarn linc and prettier scripts.

Community
Basic