receiving-code-review

Guides verification and reasoned response when receiving code review feedback before implementing suggestions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often triggers performative agreement or blind implementation, leading to broken code, wasted effort on unused features, and missed clarification on unclear items. This Skill enforces technical verification and reasoned evaluation before any change is made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback criteria and YAGNI checks. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing, you check build targets, discover backward-compatibility requirements, and push back with technical reasoning or ask a clarifying question. ## Quick Start Use the receiving-code-review skill to evaluate this pull request feedback before I implement any of the 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 before implementing it?

Read the full feedback, restate the requirement in your own words, verify it against the actual codebase, then respond with technical acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

How do I handle unclear items in a multi-item code review?

Stop and ask for clarification on the unclear items before implementing anything. Partial understanding leads to wrong implementations because items are often related, so clarify everything first, then proceed.

When should I push back on a code review suggestion?

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

Should I treat external reviewer feedback differently from my team lead's feedback?

Yes. Feedback from a trusted human partner can be implemented after understanding, while external reviewer 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 endpoint for pull request comment replies, not as a top-level PR comment. This keeps the discussion attached to the specific line of code being reviewed.