receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often involve ambiguous feedback that leads to blind implementations. This Skill enforces a structured, technical approach to interpret feedback, verify against the codebase, and respond with reasoned pushback when needed.

Core Features & Use Cases

  • Verify feedback before acting, restating requirements, and validating against the current code to avoid blind implementations.
  • Structured response pattern including READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT steps for each item.
  • Use case: you receive unclear feedback from a reviewer; you restate the requirement, check applicability to the codebase, and implement changes one item at a time after validation.

Quick Start

Walk through each feedback item by restating the requirement, verifying against the codebase, and implementing changes one at a time after validation.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle ambiguous code review feedback without blindly implementing changes?

To handle ambiguous code review feedback, you should restate the requirement, verify the item against the current codebase, evaluate its applicability, and implement changes one by one to avoid blind implementations.

What is the best way to push back on a pull request review comment?

The best way to push back on a pull request review comment is to follow a structured response pattern: read, understand, verify, evaluate, and respond with reasoned pushback before implementing any requested changes.

How do I verify code review items against an existing codebase?

You verify code review items by restating the technical requirement, checking its applicability against the current codebase, and validating the necessity of the change before proceeding with implementation.

What steps should I follow to resolve unclear code review comments?

To resolve unclear code review comments, follow a six-step pattern: READ the feedback, UNDERSTAND the intent, VERIFY against the codebase, EVALUATE the technical validity, RESPOND with pushback if needed, and IMPLEMENT validated changes.

How to prevent performative agreement when responding to code review feedback?

To prevent performative agreement during code reviews, enforce quality guardrails that require technical rigor and codebase verification before accepting and acting on any reviewer feedback.

When should I escalate unclear feedback during a software engineering code review?

You should escalate unclear code review feedback when verification against the codebase fails to resolve the ambiguity, utilizing defined escalation rules to ensure technical rigor and prevent blind implementations.