receiving-code-review

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

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Viranya2006/Lumen --skill receiving-code-review-viranya2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Viranya2006/Lumen/tree/main/SKILLS/receiving-code-review
Command: npx skills add https://github.com/Viranya2006/Lumen --skill receiving-code-review-viranya2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to broken code, misunderstood requirements, and wasted effort. This Skill enforces a disciplined response pattern: verify feedback against the actual codebase before implementing anything. ## 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 protocols for trusted human partner feedback versus external reviewer suggestions, including pushback guidance with technical reasoning. - YAGNI and Unclear Feedback Checks: Grep the codebase before adding suggested features, and stop to clarify ambiguous items before implementing anything. - Use Case: A reviewer leaves six comments on your pull request, two of which are unclear and one suggesting an unused endpoint. The Skill directs you to clarify the unclear items first, challenge the unused endpoint with YAGNI reasoning, then implement the valid fixes one at a time. ## Quick Start Use the receiving-code-review skill to help me evaluate and respond to the review comments on my pull request 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 do I respond to code review feedback professionally?

Restate the technical requirement, verify it against your codebase, then either implement it or push back with technical reasoning. Avoid performative phrases like "great point" and let the code changes demonstrate you understood the feedback.

How to 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, so state which items you understand and which need clarification.

When should I push back on code review suggestions?

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 rather than being defensive.

Should I implement all review feedback at once?

No. Implement one item at a time and test each fix individually, ordering work by blocking issues first, then simple fixes, then complex refactoring. Batch implementation without testing hides regressions.

How do I reply to inline GitHub review comments?

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