receiving-code-review

Guides verification and implementation of code review feedback with technical rigor.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to two failure modes: performative agreement without verification, or blind implementation of suggestions that may be wrong for the codebase. This Skill enforces a disciplined response pattern so feedback is evaluated technically before any code changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback guidance and YAGNI checks. - Use Case: A reviewer suggests removing legacy code or adding a metrics endpoint. Instead of agreeing immediately, you grep the codebase, discover the legacy code is needed for backward compatibility or the endpoint is never called, and respond with technical reasoning. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my pull request before implementing anything.

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 before implementing it?

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, evaluate whether it is technically sound, then respond and implement one item at a time. Never agree performatively or implement before verification.

How do I handle unclear code review comments?

Stop and ask for clarification before implementing anything, even if other items are clear. Partial understanding leads to wrong implementations because feedback items are often related.

When should I push back on a code review suggestion?

Push back when a suggestion breaks existing functionality, violates YAGNI, is technically incorrect for your stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests rather than being defensive.

Should external reviewer feedback be treated differently from my team lead's feedback?

Yes. Trusted partner feedback can be implemented after understanding, while external suggestions require verification against the codebase first. If external feedback conflicts with prior decisions, discuss with your partner before proceeding.

How do I reply to inline review comments on GitHub pull requests?

Reply within the comment thread using the GitHub API replies endpoint for that comment ID, not as a top-level PR comment. This keeps the discussion attached to the specific code being reviewed.