receiving-code-review

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

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/johsquaree/claude-basic-docs --skill receiving-code-review-johsquaree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/johsquaree/claude-basic-docs/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/johsquaree/claude-basic-docs --skill receiving-code-review-johsquaree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to performative agreement, blind implementation of questionable suggestions, or partial fixes when items are unclear. This Skill enforces a verify-before-implement workflow so feedback is evaluated against the actual codebase before any changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Source-Specific Handling: Distinguishes trusted feedback from your human partner versus external reviewer suggestions that require skepticism and verification. - Pushback and YAGNI Checks: Provides criteria for pushing back with technical reasoning and grepping the codebase to reject unused "professional" features. - Use Case: A reviewer asks you to remove legacy code. Instead of agreeing, you check build targets, discover backward-compatibility requirements, and respond with the technical constraint plus a concrete question. ## Quick Start Use the receiving-code-review skill to evaluate and respond to this pull request review feedback before implementing any 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 complete feedback, restate the requirement in your own words, verify it against the 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 code review comments?

Stop and ask for clarification before implementing anything. Partial understanding leads to wrong implementations, so state which items you understand and request clarification on the rest before proceeding.

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 handle external reviewer feedback differently from my team lead's feedback?

Yes. Feedback from your human partner is trusted and can be implemented after understanding, while external reviewer suggestions require verification against the codebase, platform compatibility, and existing functionality first.

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 code line being reviewed.