receiving-code-review

Verify code review feedback against the codebase before implementing changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents blind or performative agreement and avoids incorrect implementations by requiring verification, clarification, and prioritized action when receiving code review feedback.

Core Features & Use Cases

  • Structured Response Pattern: Read, restate, verify, evaluate, respond, and implement one item at a time with tests.
  • Source-Specific Handling: Different checks and skepticism levels for human partners versus external reviewers, including YAGNI verification and compatibility checks.
  • Pushback & Correction Guidance: How to push back with technical reasoning, when to escalate, and how to acknowledge and correct mistakes concisely.

Quick Start

Restate unclear review items, verify them against the codebase, ask clarifying questions for anything ambiguous, then implement fixes in prioritized order with tests.

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?

To verify code review feedback, restate unclear items, check suggestions against the codebase, ask clarifying questions for ambiguities, and implement fixes in prioritized order with tests. This prevents blind agreement and incorrect implementations.

What is the best way to handle multiple items in pull request feedback?

Handling multiple pull request feedback items requires a structured response pattern: read, restate, verify, evaluate, and respond to each item individually. Implement changes one at a time in a prioritized order, ensuring tests accompany each fix.

How to push back on incorrect code review suggestions?

Push back on incorrect code review suggestions by providing technical reasoning based on codebase verification. Acknowledge and correct your own mistakes concisely, and know when to escalate disagreements rather than blindly implementing invalid changes.

When should I apply YAGNI verification to code review comments?

Apply YAGNI verification to code review comments when evaluating suggestions from external reviewers. This checks whether requested features are actually necessary, preventing unnecessary implementation overhead and maintaining compatibility with existing codebase requirements.

Does handling code review feedback require different checks for internal versus external reviewers?

Handling code review feedback requires different skepticism levels for internal partners versus external reviewers. Source-specific checks involve verifying YAGNI principles and compatibility constraints more rigorously for external suggestions to ensure correctness.