skills.rest
venhdev
venhdevCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback against codebase reality before implementing changes.

Updated May 3, 2026
Search Tags:#code review#pull request#YAGNI#technical rigor#pushback#code verification#feedback response
One-click install
npx skills add https://github.com/venhdev/skills --skill receiving-code-review-venhdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/venhdev/skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/venhdev/skills --skill receiving-code-review-venhdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When receiving code review feedback, developers often default to performative agreement or blindly implement suggestions without verifying if they are technically sound for the specific codebase, leading to broken functionality, wasted work, or violations of existing architectural decisions. This Skill eliminates that risk by enforcing a rigorous, verification-first workflow for processing all code review feedback.

Core Features & Use Cases

  • Structured Response Pattern: A step-by-step process (read, understand, verify, evaluate, respond, implement) that eliminates emotional reactions and ensures technical rigor at every step.
  • Scenario-Specific Guidance: Tailored rules for feedback from internal human partners vs. external reviewers, including YAGNI checks for unnecessary feature suggestions and protocols for handling unclear or conflicting feedback.
  • Pushback & Correction Frameworks: Clear guidance for pushing back against technically incorrect feedback with reasoned arguments, and for gracefully correcting your own pushback if you were wrong, without performative apologies.
  • Use Case: For example, if an external reviewer suggests removing legacy code, this Skill guides you to first check if the code is required for backward compatibility with supported platforms before deleting it, rather than agreeing immediately.

Quick Start

Use the receiving-code-review skill to evaluate the code review feedback on your current pull request before implementing any suggested changes.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How should I respond to code review feedback without blindly implementing suggestions?▼

Respond to code review feedback using a verification-first workflow: read, understand, verify against the codebase, evaluate technical soundness, and then implement or pushback. This prevents performative agreement and ensures suggestions align with architectural decisions.

What is the best way to pushback on technically incorrect code review comments?▼

Pushback on incorrect code review comments by providing reasoned arguments based on codebase reality and existing architectural decisions. If your pushback is wrong, correct it gracefully with factual corrections rather than performative apologies.

How do I validate YAGNI when a reviewer suggests adding new features to my pull request?▼

Validate YAGNI by checking if the suggested features are actually necessary for the current codebase scope. Apply technical rigor to verify whether the proposed additions solve a real problem or introduce unnecessary complexity before implementing them.

When should I check backward compatibility before removing legacy code suggested in a code review?▼

Check backward compatibility before removing legacy code whenever an external reviewer suggests deletion. Verify if the code is required for supported platforms or existing functionality before modifying it, rather than agreeing immediately to the review feedback.

How do I handle unclear or conflicting code review comments from multiple reviewers?▼

Handle unclear or conflicting code review comments by applying a structured evaluation process. Verify each suggestion against codebase reality, check existing architectural decisions, and use reasoned responses to clarify conflicts before making any code modifications.

Related Skills

Explore More Software Engineering Skills→
xhyqaqxhyqaq
63

receiving-code-review

Verifies GitHub pull-request feedback before implementing code changes.

Community
Intermediate
tonombtonomb

resolving-merge-conflicts

Resolve git merge and rebase conflicts by analyzing commit history and reconciling code changes.

Community
Intermediate
caiohbfurtadocaiohbfurtado

grill-with-docs

Validate project plans against domain models and architectural documentation.

Community
Advanced
flosrnflosrn

receiving-code-review

Verify and implement code review feedback with reasoned technical responses.

Community
Intermediate