receiving-code-review

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

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill receiving-code-review-aarushishah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/AarushiShah/coding-agents-databricks-apps/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/AarushiShah/coding-agents-databricks-apps --skill receiving-code-review-aarushishah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation of code review feedback by enforcing a verify-first workflow, eliminating performative agreement and ensuring suggestions are technically sound for the specific 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: Differentiates between trusted feedback from your human partner and external reviewer suggestions that require skeptical verification against the codebase. - YAGNI and Pushback Rules: Checks whether suggested features are actually used before implementing, and provides technical reasoning patterns for pushing back on incorrect feedback. - Use Case: When a reviewer on a GitHub pull request suggests six changes and two are unclear, the skill instructs you to clarify items 4 and 5 before implementing anything, then fix items in order of blocking issues, simple fixes, and complex refactors. ## Quick Start Apply the receiving-code-review skill to evaluate the reviewer 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 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, evaluate whether it is technically sound, then respond with technical acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

What should I do when code review feedback is unclear?

Stop and ask for clarification before implementing anything. Partial understanding leads to wrong implementation because items may be related. State which items you understand and which need clarification before proceeding.

When is it appropriate to push back on a code review suggestion?

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

How do I handle feedback from external reviewers versus my team lead?

Feedback from your human partner is trusted and can be implemented after understanding, while external reviewer suggestions require verification against the codebase first. If external feedback conflicts with your partner's prior decisions, stop and discuss with your partner 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 rather than posting a top-level PR comment. This keeps the discussion attached to the specific line of code being reviewed.