receiving-code-review

Guides verification and implementation of code review feedback with technical rigor.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill receiving-code-review-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/superpowers/receiving-code-review
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill receiving-code-review-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI assistants often respond with sycophantic agreement or blindly implement suggestions without verifying them against the actual codebase, leading to broken functionality, unnecessary features, and misunderstood requirements. ## Core Features & Use Cases - Verify Before Implementing: Enforces a read-understand-verify-evaluate-respond workflow so feedback is checked against the actual codebase before any changes are made. - Source-Based Handling: Distinguishes between trusted partner feedback and external reviewer feedback, applying extra scrutiny and YAGNI checks to external suggestions. - Structured Pushback: Provides concrete guidance on when and how to disagree with reviewers using technical reasoning, including a graceful path for correcting your own rebuttals when wrong. - Use Case: A reviewer asks you to delete legacy code and implement six fixes. Instead of agreeing immediately, you grep the codebase, discover the legacy code is needed for backward compatibility, clarify the two ambiguous items, then implement the verified fixes one at a time with tests. ## Quick Start Apply the receiving-code-review skill to evaluate and respond to the review comments on my pull request before making any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How should I respond to code review feedback as a developer?

Read the feedback fully, restate the requirement in your own words, verify it against the actual codebase, then respond with technical confirmation or a reasoned rebuttal. Implement fixes one at a time with testing rather than batch-implementing everything.

How do I handle unclear code review comments?

Stop and ask for clarification before implementing anything, even if other items are clear. Partial understanding leads to incorrect implementation since feedback items are often interrelated.

When should I push back on a code review suggestion?

Push back when a suggestion breaks existing functionality, violates YAGNI for unused features, is technically incorrect for your stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests, not defensive emotion.

Should I treat external reviewer feedback differently from teammate feedback?

Yes. Trusted partner feedback can be implemented after understanding, but external feedback should be verified first: check technical correctness, whether it breaks existing behavior, and whether the reviewer has full context of the codebase.

What is the YAGNI check for code review suggestions?

When a reviewer suggests properly implementing a feature, grep the codebase for actual usage first. If nothing calls the interface, propose deleting it instead of building it out, avoiding unnecessary code.