receiving-code-review

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

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/Yvesdefaria/GymLab --skill receiving-code-review-yvesdefaria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Yvesdefaria/GymLab/tree/main/.opencode/skills/receiving-code-review
Command: npx skills add https://github.com/Yvesdefaria/GymLab --skill receiving-code-review-yvesdefaria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI agents 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, respond, and implement one item at a time. ## Core Features & Use Cases - Structured Response Pattern: A six-step workflow (read, understand, verify, evaluate, respond, implement) that prevents blind implementation of review comments. - Source-Specific Handling: Different rules for feedback from a trusted human partner versus external reviewers, including pushback guidance and YAGNI checks for unused features. - Forbidden Response Detection: Explicitly bans performative phrases like "You're absolutely right!" and gratitude expressions, replacing them with technical acknowledgment or direct action. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing immediately, the agent checks build targets, discovers backward-compatibility requirements, and responds with technical reasoning before changing anything. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review 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 as an AI agent?

Follow a six-step pattern: read the full feedback, restate the requirement, verify it against the codebase, evaluate technical soundness, respond with technical acknowledgment or reasoned pushback, then implement one item at a time with testing.

How do I handle unclear code review comments before implementing?

Stop and ask for clarification on every unclear item before implementing anything. Partial understanding leads to wrong implementations because feedback items are often related, so clarify all items 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 the stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests.

Should I treat external reviewer feedback the same as my project owner's feedback?

No. Feedback from your trusted human partner can be implemented after understanding, while external reviewer feedback requires verification against the codebase, platform compatibility checks, and skepticism about missing context.

Why should I avoid saying thanks or agreeing in code review replies?

Performative agreement like "You're absolutely right!" adds no technical value and can precede blind implementation. State the fix or requirement factually instead, letting the code change itself demonstrate the feedback was heard.