receiving-code-review

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

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/kangjuhyup/study --skill receiving-code-review-kangjuhyup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/kangjuhyup/study/tree/main/scoped-superpowers-ab/workflow-code-benchmark/fixture/workflows/full/skills/receiving-code-review
Command: npx skills add https://github.com/kangjuhyup/study --skill receiving-code-review-kangjuhyup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often triggers performative agreement or blind implementation, leading to unverified changes, broken functionality, and wasted effort on unnecessary features. This Skill enforces a disciplined response pattern: verify before implementing, ask before assuming, and push back with technical reasoning when suggestions are wrong. ## 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: Differentiates trusted feedback from your human partner versus external reviewer suggestions that require skepticism and verification. - YAGNI Enforcement: Checks whether suggested features are actually used in the codebase before implementing them. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing immediately, you check build targets and discover the code is needed for backward compatibility, then push back with technical reasoning. ## 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?

Read the complete 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 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 for unused features, is technically incorrect for your stack, or conflicts with architectural decisions. Use technical reasoning and reference working tests or code.

Should I treat external reviewer feedback the same as my team lead's?

No. Feedback from your human partner is trusted and can be implemented after understanding. External reviewer suggestions require verification: check correctness for your codebase, platform compatibility, and whether the reviewer understands full context.

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.