receiving-code-review

Evaluates code review feedback against codebase reality before implementing changes.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill receiving-code-review-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.codex/plugins/cache/openai-curated/superpowers/dc902811/skills/receiving-code-review
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill receiving-code-review-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When receiving code review feedback, AI agents often respond with performative agreement or blindly implement suggestions that may be unclear, technically wrong, or conflict with existing architecture. This Skill enforces technical rigor: verify before implementing, ask before assuming, and push back with reasoning when feedback is incorrect. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Distinguishes trusted feedback from your human partner versus external reviewer suggestions that require skeptical verification against the codebase. - YAGNI and Pushback Checks: Greps for actual usage before building "proper" features and provides technical reasoning patterns for declining incorrect suggestions. - Use Case: A reviewer asks to remove legacy code. Instead of agreeing, you check build targets, discover backward-compatibility requirements, and respond with a technically grounded question before changing anything. ## Quick Start Use the receiving-code-review skill to evaluate this pull request feedback and tell me which items to implement, clarify, or push back on.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I respond to code review feedback as an AI agent?▼

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, then respond with technical acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on any unclear items before implementing anything. Partial understanding leads to wrong implementation because feedback items are often related, so clarify all items first.

Should I implement every suggestion from external reviewers?▼

No. External feedback is a suggestion to evaluate, not an order. Check whether it is technically correct for this codebase, breaks existing functionality, or conflicts with prior architectural decisions before implementing.

When should I push back on code review feedback?▼

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

How do I reply to inline review comments on GitHub?▼

Reply within the comment thread using the GitHub API endpoint for pull request comment replies, not as a top-level PR comment. This keeps the discussion attached to the specific code line being reviewed.