receiving-code-review

Verify and evaluate code review feedback against codebase reality before implementation.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/mezivillager/hacer --skill receiving-code-review-mezivillager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/mezivillager/hacer/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/mezivillager/hacer --skill receiving-code-review-mezivillager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you navigate code review feedback by ensuring technical rigor and verification before implementation, preventing performative agreement or blind execution of potentially flawed suggestions.

Core Features & Use Cases

  • Technical Verification: Empowers you to critically assess code review suggestions against the codebase's reality.
  • Reasoned Pushback: Provides a framework for constructively challenging feedback that is unclear, incorrect, or not aligned with project goals.
  • Structured Implementation: Guides you to implement verified feedback efficiently and safely, one item at a time.
  • Use Case: When an external reviewer suggests a significant architectural change, this Skill prompts you to verify its necessity and impact against current project requirements and your human partner's directives before proceeding.

Quick Start

Use the receiving-code-review skill to evaluate feedback from an external reviewer on the latest pull request.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
What is the best way to handle code review feedback without blindly implementing it?

The best way to handle code review feedback is to apply technical verification before implementation, checking suggestions against codebase reality and project context to prevent performative agreement and avoid executing flawed instructions.

How do I verify technical suggestions from an external reviewer before making changes?

To verify technical suggestions from an external reviewer, evaluate the feedback against existing functionality and current project requirements, ensuring the proposed architectural changes align with actual codebase reality and human partner directives.

How do you constructively pushback on unclear code review comments?

To constructively pushback on unclear code review comments, use a structured protocol to evaluate the feedback, check it against existing functionality, and provide a reasoned response rather than performative agreement.

When should I avoid implementing code review suggestions immediately?

You should avoid implementing code review suggestions immediately when an external reviewer proposes significant architectural changes, requiring you to first verify their necessity and impact against current project requirements.

What is a structured protocol for processing code review feedback?

A structured protocol for processing code review feedback involves sequentially understanding, verifying, evaluating, and responding to each item, ensuring every suggestion is checked against codebase reality before structured implementation.