skills.rest
zhexulong
zhexulongCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Guide developers through a structured process for handling code review feedback.

5|Updated Jun 10, 2026
Search Tags:#code review#technical verification#feedback handling#implementation order#response pattern
One-click install
npx skills add https://github.com/zhexulong/bdd-superpowers --skill receiving-code-review-zhexulong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/zhexulong/bdd-superpowers/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/zhexulong/bdd-superpowers --skill receiving-code-review-zhexulong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers handle code review feedback more effectively, ensuring technical correctness and reducing the risk of misinterpretation or incorrect implementation.

Core Features & Use Cases

  • Technical Verification: Prompts developers to verify feedback against the codebase before implementation.
  • Response Pattern: Provides a structured response pattern for handling feedback, including reading, understanding, verifying, evaluating, responding, and implementing.
  • Handling Unclear Feedback: Offers guidance on how to handle unclear feedback and the importance of seeking clarification.
  • Source-Specific Handling: Differentiates between feedback from human partners and external reviewers, with specific handling instructions for each.
  • YAGNI Check: Encourages developers to question the necessity of suggested features and avoid unnecessary implementation.
  • Implementation Order: Suggests a structured order for implementing feedback, emphasizing testing and verification.
  • When To Push Back: Defines scenarios where pushing back is appropriate and provides guidelines on how to do so effectively.
  • Acknowledging Correct Feedback: Offers guidance on how to acknowledge correct feedback without using performative agreement.
  • Gracefully Correcting Pushback: Provides a framework for correcting mistakes when pushback was incorrect.
  • Common Mistakes: Lists common mistakes made during code review and their fixes.
  • Real Examples: Provides real-world examples of good and bad practices in code review feedback handling.

Quick Start

Activate the 'receiving-code-review' skill and follow the structured response pattern when receiving code review feedback.

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 without misinterpreting technical requirements?▼

To handle code review feedback effectively, verify suggestions against the codebase before implementation, evaluate necessity, and follow a structured response pattern of reading, understanding, verifying, evaluating, responding, and implementing.

What is the best way to respond to unclear code review comments?▼

The best way to respond to unclear code review comments is to seek clarification proactively, differentiate between human partner and external reviewer feedback, and verify the technical context before writing any implementation code.

When should I push back on code review feedback?▼

You should push back on code review feedback when suggested features fail the YAGNI check, or when technical verification proves the suggestion incorrect, using a structured framework to communicate the pushback effectively.

How do I acknowledge correct code review feedback without performative agreement?▼

To acknowledge correct code review feedback without performative agreement, directly confirm the technical validity of the point, implement the necessary changes in a structured order, and avoid using unnecessary apologetic language.

What are common mistakes when implementing code review feedback?▼

Common mistakes when implementing code review feedback include skipping technical verification against the codebase, failing to question unnecessary features, and implementing suggestions without a structured testing and verification order.

Can I correct my pushback if I made a mistake during code review?▼

Yes, you can correct pushback mistakes during code review by applying a framework for gracefully correcting incorrect pushback, acknowledging the technical oversight, and proceeding with the accurate implementation.

Related Skills

Explore More Software Engineering Skills→
gmliaogmliao
1

receiving-code-review

Guide developers through a six-step code-review feedback response protocol.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

run-tests

Execute Mojo or Python test suites and generate validation reports.

Official
Basic
jchildreejchildree
1

receiving-code-review

Verify code review feedback against the codebase before responding.

Community
Intermediate
AAbdulghanyAAbdulghany

code-review

Automate pull request reviews with role-based gating and human sign-off.

Community
Advanced