ywc-receive-review

Name: ywc-receive-review
Availability: InStock
Author: yongwoon

Verify code review feedback against the codebase before implementing changes.

8|1|Updated May 13, 2026

Search Tags:#automation #quality assurance #code review #pull request #verification #technical discipline

Ready to run

npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-receive-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ywc-receive-review
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-receive-review
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-receive-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents the common LLM failure mode of performative agreement, where the AI blindly accepts and implements incorrect or context-unaware code review suggestions, leading to broken functionality and wasted effort.

Core Features & Use Cases

Iron Law Enforcement: Forces a strict 6-step verification process (Read, Understand, Verify, Evaluate, Respond, Implement) for every review comment.
Technical Pushback: Provides templates to professionally challenge suggestions that break functionality, violate YAGNI, or conflict with architectural decisions.
Use Case: When receiving feedback from a human partner or an automated tool like CodeRabbit, use this skill to ensure you verify the claim against the codebase before agreeing or implementing any changes.

Quick Start

Activate the ywc-receive-review skill to verify the incoming review feedback and ensure all responses are backed by technical evidence rather than performative agreement.

Frequently Asked Questions about ywc-receive-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent AI from blindly accepting incorrect code review feedback?▼

To prevent performative agreement in code review, enforce a strict 6-step technical verification protocol that requires reading, understanding, and verifying claims against the codebase before implementing any changes.

What is the best way to enforce technical verification for automated pull request reviews?▼

The best way to enforce technical verification for pull request reviews is to apply a systematic process that evaluates every review comment against the codebase, ensuring responses are backed by technical evidence rather than non-technical acknowledgment.

How do I push back on code review suggestions that break functionality or violate YAGNI?▼

To push back on code review suggestions that break functionality or violate YAGNI, use professional technical pushback templates that require evidence-based justification, ensuring architectural integrity is maintained during the code review process.

Can I use a verification protocol for code review feedback from automated tools and human partners?▼

Yes, a technical verification protocol can be applied to both human and automated code review workflows, ensuring that all feedback from tools or partners is systematically verified for technical accuracy before implementation.

Why does my LLM implement context-unaware code review suggestions without verifying them?▼

LLMs implement context-unaware code review suggestions due to performative agreement failure modes, which can be resolved by enforcing a rigorous verification protocol that eliminates non-technical acknowledgment phrases.

What are the limitations of relying on automated code review without technical verification?▼

Without technical verification, automated code review risks performative agreement and blind implementation of incorrect suggestions, leading to broken functionality and wasted effort due to unverified architectural conflicts.