receiving-code-review

Apply a six-step response pattern to code review feedback.

66|20|Updated Dec 30, 2025

Search Tags:#communication #verification #code-review #pull-request #technical-rigor #feedback-processing

Ready to run

npx skills add https://github.com/cooker/wxHm --skill receiving-code-review-cooker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/cooker/wxHm/tree/main/.cursor/skills/receiving-code-review
Command: npx skills add https://github.com/cooker/wxHm --skill receiving-code-review-cooker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback is often ambiguous or noisy; this Skill provides a disciplined approach to interpret and respond to feedback without compromising technical correctness.

Core Features & Use Cases

Structured feedback handling: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.
Clarification prompts: If unclear, ask questions before acting.
Safer, incremental changes: Implement one item at a time and verify.
Consistency across reviews: Standardizes responses to reviews across projects.

Quick Start

Apply the receiving-code-review process to a code-review feedback: read, understand, verify against the codebase, evaluate for technical correctness, respond with reasoning or pushback, and implement changes one item at a time with tests.

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 code review feedback systematically before making changes?▼

To handle code review feedback systematically, follow a structured process: read, understand, verify against the codebase, evaluate for technical correctness, respond with reasoning, and implement changes one item at a time.

What is the best way to respond to ambiguous pull-request comments?▼

The best way to respond to ambiguous pull-request comments is to use clarification prompts. Ask targeted questions to ensure clarity and technical correctness before implementing any changes.

How do I verify code review feedback against my codebase?▼

You verify code review feedback by evaluating it against the existing codebase during the verification step. This ensures the feedback is technically correct before you respond or implement changes.

Can I push back on code review suggestions if they are technically incorrect?▼

Yes, you can push back on code review suggestions if they are technically incorrect. The evaluation step requires you to assess feedback for technical correctness and respond with clear reasoning.

When should I ask questions instead of immediately implementing code review changes?▼

You should ask questions instead of implementing code review changes when the feedback is ambiguous or noisy. Clarification prompts ensure you understand the intent before acting on any review item.

How do I ensure consistency when processing code review feedback across different projects?▼

To ensure consistency when processing code review feedback across different projects, apply a standardized six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT for every review item.