receiving-code-review

Guides verification and reasoned responses when receiving code review feedback.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill receiving-code-review-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/receiving-code-review
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill receiving-code-review-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often triggers two failure modes: performative agreement ("You're absolutely right!") or blind implementation of suggestions that may be wrong for the codebase. This Skill enforces technical rigor when receiving review comments, ensuring every suggestion is verified against the actual codebase before being implemented. ## 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 with technical reasoning when suggestions break functionality or violate YAGNI. - Unclear Feedback Protocol: Stops all implementation when any item is unclear and requests clarification before proceeding, preventing partial or wrong implementations. - Use Case: A reviewer on your GitHub PR suggests removing legacy code and adding a metrics endpoint. Instead of agreeing, you verify the legacy code is needed for backward compatibility and grep the codebase to find nothing calls the metrics endpoint, then reply in the comment thread with reasoned pushback. ## Quick Start Apply the receiving-code-review skill to evaluate and respond to the review comments on my current pull request.

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 on a pull request?

Read all feedback completely, restate each requirement in your own words, verify it against the codebase, then implement one item at a time with individual testing. Avoid performative agreement like "Great point!" and instead state the fix or ask clarifying questions.

How do I handle unclear code review comments?

Stop and ask for clarification before implementing anything when any item is unclear. Partial understanding leads to wrong implementations because items are often related, so clarify all ambiguous points 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 rather than being defensive.

Should I implement every suggestion from external reviewers?

No. Verify external suggestions against your codebase first: check technical correctness, platform compatibility, and whether the reviewer understands the full context. If you cannot verify something, state the limitation and ask for direction.

How do I reply to inline review comments on GitHub?

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