receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated Oct 28, 2025
One-click install
npx skills add https://github.com/AlabamaMike/copilot-agents --skill receiving-code-review-alabamamike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/AlabamaMike/copilot-agents/tree/main/.codex/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/AlabamaMike/copilot-agents --skill receiving-code-review-alabamamike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receiving code review feedback can be challenging, often leading to performative agreement, blind implementation, or unclear communication. This skill enforces a rigorous, technical approach to receiving feedback, mandating verification before implementation, clarifying unclear items, and providing reasoned pushback when necessary, ensuring technical correctness over social comfort.

Core Features & Use Cases

  • Technical Verification: Requires verifying feedback against codebase reality before implementing.
  • Clarification Protocol: Guides asking for clarification on unclear items before proceeding.
  • Reasoned Pushback: Provides guidance on when and how to technically push back on questionable suggestions.
  • No Performative Agreement: Explicitly forbids emotional or performative responses, focusing on technical facts.
  • Use Case: When you receive code review feedback, use this skill to systematically process each item, ensuring you understand, verify, and respond technically, leading to better code and clear communication.

Quick Start

Use the receiving-code-review skill to process the feedback on the 'user-authentication' pull request.

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 without just agreeing with everything?▼

Respond to code review feedback by verifying each item against your codebase before implementing. Restate requirements for clarity, validate them technically, and provide reasoned pushback when suggestions lack technical merit—prioritizing correctness over social comfort.

What's the best way to handle unclear or ambiguous code review comments?▼

Use a clarification protocol: ask reviewers to explain unclear feedback before proceeding. Restating their point back ensures shared understanding and prevents misinterpretation that leads to wasted implementation effort.

How do I implement code review feedback systematically without making mistakes?▼

Process feedback one item at a time. Verify each suggestion against your codebase, test staged changes individually, and document your reasoning. This disciplined approach prevents premature changes and confirms technical correctness.

When is it appropriate to push back on code review suggestions?▼

Push back when feedback contradicts codebase reality, introduces unnecessary complexity, or lacks technical justification. Present facts and reasoning to support your position rather than emotional resistance.

Can I use this approach across different development workflows and team sizes?▼

Yes. The receiving-code-review skill applies across software projects and teams. Its disciplined verification and clarification protocols work regardless of project size or team structure.