bee:receiving-code-review

Verify code review feedback for technical correctness before implementation.

2|1|Updated Mar 3, 2026

Search Tags:#code review #feedback #implementation #verification #pushback #technical correctness

Ready to run

npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-receiving-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bee:receiving-code-review
Source: https://github.com/luanrodrigues/ia-frmwrk/tree/main/default/skills/receiving-code-review
Command: npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the automatic and uncritical implementation of code review suggestions, ensuring technical verification and preventing performative agreement.

Core Features & Use Cases

Technical Verification: Ensures suggestions are technically sound and appropriate for the codebase before implementation.
Clarification Protocol: Guides the user on how to handle unclear feedback.
Pushback Strategy: Provides clear guidelines on when and how to push back against incorrect suggestions.
Use Case: When a reviewer suggests a change, this Skill prompts you to verify its correctness against the codebase, ask clarifying questions if needed, and only then proceed with implementation, preventing the introduction of errors or unnecessary changes.

Quick Start

Use the bee:receiving-code-review skill to evaluate feedback received on your latest code commit.

Frequently Asked Questions about bee:receiving-code-review

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

FAQPage Schema

How do I verify code review feedback before implementing changes?▼

To verify code review feedback, you must understand the suggestion, check its technical correctness against the codebase, and evaluate its appropriateness before proceeding with implementation to prevent introducing errors.

What is the best way to push back on incorrect code review comments?▼

The best way to push back on incorrect code review comments is to prioritize technical correctness over social comfort, providing a technical acknowledgment or reasoned pushback once you have verified the suggestion is unsuitable for the codebase.

How do I stop performative agreement during code reviews?▼

To stop performative agreement during code reviews, apply a strict response pattern that mandates understanding, technical verification, and evaluation of feedback before any implementation or acknowledgment occurs.

What should I do if code review feedback is unclear?▼

If code review feedback is unclear, you should use a clarification protocol to ask the reviewer questions, ensuring you fully understand the suggestion before attempting to verify its technical correctness or implementing it.

When should I avoid blindly implementing code review suggestions?▼

You should avoid blindly implementing code review suggestions in all scenarios, as uncritical adoption prevents technical verification and risks introducing unnecessary changes or errors into the codebase.

Does this code review verification process work for all types of feedback?▼

Yes, this code review verification process applies to all code review scenarios, emphasizing technical correctness over social comfort and requiring a consistent pattern of understanding, verification, and evaluation for every piece of feedback.