receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/bbohhu-prog/waxs --skill receiving-code-review-bbohhu-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/bbohhu-prog/waxs/tree/main/.claude/skills/superpowers/receiving-code-review
Command: npx skills add https://github.com/bbohhu-prog/waxs --skill receiving-code-review-bbohhu-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When receiving code-review feedback, teams often encounter unclear or technically questionable guidance. This skill emphasizes technical rigor, verification, and disciplined execution to avoid blind agreement or premature changes.

Core Features & Use Cases

  • Restatement & Clarification: Restate the feedback to ensure mutual understanding before taking action.
  • Technical Verification: Check the feedback against the codebase, tests, and project constraints to assess feasibility and impact.
  • Incremental Implementation: Address feedback item by item with targeted changes and validations, reducing risk.
  • Defensive Pushback: Offer reasoned technical objections when feedback is incorrect or unsafe.

Quick Start

Provide a clear, actionable plan to respond to code-review feedback with technical rigor.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I verify code review feedback before implementing changes?

Verify code review feedback by restating the requirement, checking it against the codebase and tests, and evaluating technical feasibility to ensure changes are sound before implementation.

What is the best way to handle incorrect or technically questionable code review comments?

Handle questionable code review comments by providing defensive pushback with reasoned technical objections, ensuring you do not blindly agree or make premature changes to the codebase.

How do I implement code review suggestions safely in a pull request?

Implement pull request suggestions safely by addressing feedback item by item with targeted changes and validations, reducing risk through incremental execution rather than bulk updates.

Why should I restate code review feedback before taking action?

Restating code review feedback ensures mutual understanding and clarifies the requirement before taking action, preventing miscommunication and avoiding unnecessary modifications to the codebase.

How do I push back on a code review suggestion that breaks existing tests?

Push back on suggestions that break tests by verifying the feedback against project constraints and offering defensive pushback with technical reasoning to explain why the change is unsafe.