receiving-code-review

Verify code review feedback against codebase realities before implementation.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/raduceuca/wcgw-fun --skill receiving-code-review-raduceuca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/raduceuca/wcgw-fun/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/raduceuca/wcgw-fun --skill receiving-code-review-raduceuca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you navigate code review feedback by ensuring you technically verify suggestions before blindly implementing them, especially when feedback is unclear or questionable. It promotes rigorous technical evaluation over performative agreement.

Core Features & Use Cases

  • Structured Response Pattern: Follows a clear, step-by-step process for handling feedback: Read, Understand, Verify, Evaluate, Respond, Implement.
  • Handling Ambiguity: Provides clear guidance on how to ask for clarification when feedback is unclear.
  • External Reviewer Scrutiny: Outlines specific checks for external feedback to ensure technical correctness and context alignment.
  • Use Case: You receive a code review comment suggesting a significant refactor. Instead of immediately coding, you use this Skill's pattern to first understand the suggestion, verify its necessity against the codebase, and then respond with a reasoned approach or pushback if technically unsound.

Quick Start

When receiving code review feedback, follow the pattern to read, understand, verify, evaluate, respond, and then implement each item one at a time.

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 following a structured process: read, understand, verify against codebase realities, evaluate technical soundness, respond, and then implement. This ensures suggestions are technically accurate and necessary before coding begins.

What is the best way to handle unclear code review comments?

Handle unclear code review comments by seeking clarification directly rather than guessing intent. This ensures you understand the feedback fully and can verify its technical relevance before proceeding with any codebase modifications.

How do I evaluate external code reviewer suggestions?

Evaluate external code reviewer suggestions by applying specific checks for technical correctness and context alignment. This involves verifying the feedback against codebase realities to ensure the external input is both accurate and relevant before implementation.

When should I reject code review feedback?

Reject code review feedback when it violates YAGNI principles or fails technical verification against the codebase. If evaluation shows the suggestion is unnecessary or technically unsound, reasoned pushback is required instead of blind implementation.