receiving-code-review

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

Updated May 8, 2026
One-click install
npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill receiving-code-review-tomw200082-collab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/tomw200082-collab/gt-factory-os-production-brain/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/tomw200082-collab/gt-factory-os-production-brain --skill receiving-code-review-tomw200082-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI assistants often respond with performative agreement or blindly implement suggestions without verifying them against the actual codebase. This Skill enforces a disciplined response pattern: read, understand, verify, evaluate, then respond and implement. ## Core Features & Use Cases - Structured Response Pattern: A six-step workflow (read, understand, verify, evaluate, respond, implement) that prevents premature or incorrect implementation of review feedback. - Source-Specific Handling: Different rules for feedback from a trusted human partner versus external reviewers, including pushback guidance and YAGNI checks for unused features. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing immediately, you check the build target and discover the API requires a newer OS version, then respond with technical reasoning about backward compatibility before changing anything. ## 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 as an AI assistant?▼

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, then respond with technical acknowledgment or reasoned pushback. Avoid performative phrases like "You're absolutely right" and implement one item at a time with testing.

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 prior architectural decisions. Use technical reasoning and reference working code rather than being defensive.

Should I implement every suggestion from external reviewers?▼

No. Verify each external suggestion against your codebase first: check if it breaks functionality, whether the reviewer has full context, and if it works across all platforms. 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 code line being reviewed.