receiving-code-review

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

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/Fidasek009/agents --skill receiving-code-review-fidasek009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Fidasek009/agents/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/Fidasek009/agents --skill receiving-code-review-fidasek009

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 discipline 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, then implement feedback 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. - Clarification-First Workflow: Stops implementation when any feedback item is unclear, preventing wrong partial implementations. - Use Case: A reviewer suggests removing legacy code or adding a metrics endpoint. Instead of agreeing immediately, you grep the codebase, discover backward-compatibility constraints or unused endpoints, and respond with technical reasoning or a YAGNI challenge. ## 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 because feedback items are often related, so clarify all unclear items first.

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 the same as my team lead's feedback?▼

No. Feedback from your trusted human partner 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.