receiving-code-review

Name: receiving-code-review
Availability: InStock
Author: yuma588

Verifies code review feedback before implementing each requested change step-by-step.

2|Updated Jan 7, 2026

Search Tags:#verification #quality-assurance #risk-management #code-review #pull-request #technical-communication

Ready to run

npx skills add https://github.com/yuma588/skill-gallery --skill receiving-code-review-yuma588

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/yuma588/skill-gallery/tree/main/skill-gallery-deploy/skills/community/superpower/receiving-code-review
Command: npx skills add https://github.com/yuma588/skill-gallery --skill receiving-code-review-yuma588

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receiving code review feedback can be emotionally charged and ambiguous. This Skill enforces technical rigor by guiding you to verify requirements before implementing changes.

Core Features & Use Cases

Structured six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT.
Handling unclear feedback: if unclear, stop and ask clarifying questions.
Guardrails for interactions with human reviewers, pushback with technical reasoning, and safe, incremental changes.
GitHub workflow guidance: handling inline comments, threads.

Quick Start

When you receive code review feedback, start with READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT one item at a time after verification.

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 implementing changes?▼

Handling code review feedback systematically requires a six-step process: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This ensures technical rigor by verifying requirements before applying changes.

What should I do when I receive unclear feedback on a pull request?▼

When pull request feedback is unclear, you should stop and ask clarifying questions. This prevents incorrect modifications by ensuring full technical comprehension before attempting any code adjustments.

How to push back on a code review comment with technical reasoning?▼

Pushing back on code review comments requires technical reasoning and guardrails for interactions with human reviewers. You evaluate the feedback technically and respond with safe, incremental changes.

Can I process multiple code review items at once in a pull request?▼

Processing code review items should be done one item at a time after verification. This structured approach maintains technical rigor and ensures each piece of feedback is safely evaluated before implementation.

Does this approach work for inline comments and GitHub review threads?▼

Yes, this approach provides GitHub workflow guidance for handling inline comments and threads. It applies across diverse feedback quality, ensuring strict verification before implementing changes.