receiving-code-review

Analyze code-review feedback using a six-step READ-to-IMPLEMENT process.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/ytqh/agent-skills --skill receiving-code-review-ytqh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ytqh/agent-skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/ytqh/agent-skills --skill receiving-code-review-ytqh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.

Core Features & Use Cases

  • Response Pattern: A deterministic workflow to process feedback.
  • Six-step process: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.
  • Handling Unclear Feedback: If any item is unclear, STOP and ask for clarification before proceeding with implementation.

Quick Start

Use the code-review process to respond to feedback:

  • READ: Read the feedback in full without reacting.
  • UNDERSTAND: Restate the requirement in your own words or ask for clarification.
  • VERIFY: Check the feedback against the codebase reality (open PR, touched files, tests).
  • EVALUATE: Determine if the requested change is technically sound for THIS codebase.
  • RESPOND: Provide a technical acknowledgment or reasoned pushback.
  • IMPLEMENT: Implement changes one item at a time and test each.

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 unclear code review feedback without just blindly implementing it?

Handling unclear code review feedback requires technical rigor and verification. Use a deterministic workflow to read, understand, verify, and evaluate the requested changes against your codebase reality before responding or implementing any updates.

What is the best process for responding to technically questionable pull request comments?

The best process for responding to technically questionable pull request comments involves a six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces technical clarity and reasoned pushback instead of performative agreement.

How do I verify code review suggestions against my actual codebase before making changes?

To verify code review suggestions, check the feedback against codebase reality by opening the PR, examining touched files, and running tests. Determine if the requested change is technically sound for your specific codebase before proceeding.

When should I ask for clarification during a code review instead of immediately fixing the code?

You should ask for clarification during a code review whenever any feedback item is unclear. Stop and restate the requirement in your own words or ask questions before proceeding with implementation to ensure technical accuracy.

How do I implement code review changes one item at a time without breaking my tests?

To implement code review changes safely, execute the final step by implementing changes one item at a time and testing each individually. This prevents rushed changes and ensures each modification is technically sound.