receiving-code-review

Verify, clarify, and respond to ambiguous code review feedback.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minfengyuan/harness-knowledge-base --skill receiving-code-review-minfengyuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/minfengyuan/harness-knowledge-base/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/minfengyuan/harness-knowledge-base --skill receiving-code-review-minfengyuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents performative or premature responses to code review by enforcing verification, clarification, and evidence-based decisions before implementation. It helps developers avoid blind acceptance, incorrect fixes, and scope creep when handling reviewer suggestions.

Core Features & Use Cases

  • Structured Response Pattern: Follow the READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT workflow to process feedback reliably.
  • Handling Unclear Feedback: Stop and ask clarifying questions when any item is ambiguous to avoid partial or incorrect implementation.
  • Source-Specific Guidance: Differentiate trusted partner feedback from external reviewers and apply skepticism, context checks, and YAGNI reasoning as appropriate.
  • Prioritization and Safety: Order fixes by severity (blocking, simple, complex), test each change individually, and verify no regressions before marking items done.
  • Professional Pushback: Provide concise, technical pushback with evidence when suggestions are incorrect and escalate to your human partner for architectural conflicts.

Quick Start

Assess this code review thread and produce a verified action plan listing unclear items to clarify, checks to run against the codebase, prioritized fixes, and suggested reply text.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to incorrect code review feedback on a pull request?

To respond to incorrect code review feedback, verify the suggestion against the codebase and tests, then provide concise, evidence-backed technical pushback instead of blindly accepting the review comment.

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

The best way to handle ambiguous code review comments is to stop and ask clarifying questions before implementing anything, preventing partial or incorrect fixes caused by misunderstood reviewer suggestions.

How do I prioritize fixes from GitHub code review suggestions?

Prioritize code review fixes by severity: address blocking issues first, then simple changes, and finally complex ones, testing each change individually to verify no regressions occur before marking items done.

When should I push back on external reviewer suggestions during feature development?

You should push back on external reviewer suggestions when verification proves them technically incorrect, applying skepticism, context checks, and YAGNI reasoning to avoid scope creep during feature development.

Why does YAGNI reasoning matter when resolving code review feedback?

YAGNI reasoning matters when resolving code review feedback because it prevents scope creep by evaluating whether reviewer suggestions are actually necessary, ensuring evidence-based decisions over performative or premature implementation.