receiving-code-review

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

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/BubbleBuffer/superpawers --skill receiving-code-review-bubblebuffer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/BubbleBuffer/superpawers/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/BubbleBuffer/superpawers --skill receiving-code-review-bubblebuffer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handling incoming code-review feedback can overwhelm teams and lead to ambiguous or incorrectly implemented changes. This skill ensures feedback is interpreted with rigor and verified against the codebase before acting.

Core Features & Use Cases

  • Structured feedback workflow: read, restate the requirement, verify against code, evaluate technical correctness, respond with reasoning, and implement items one by one with tests.
  • Clarification handling: identify unclear items and request clarification before making changes.
  • Technical pushback: provide solid, code-grounded justification when suggestions are unsafe, unnecessary, or misaligned with goals.
  • Reviewer-context awareness: works with both human partners and external reviewers while maintaining project constraints.

Quick Start

When you receive code-review feedback, apply the structured response pattern to verify and respond before implementing.

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 conflicting code-review feedback on a pull request?

Handling code-review feedback requires a structured workflow: read incoming comments, restate the requirement, verify it against the codebase, evaluate technical correctness, respond with reasoning, and implement changes one by one with tests.

How do I push back on code-review suggestions that are technically incorrect?

Push back on code-review suggestions by verifying the feedback against the codebase and providing solid, code-grounded justification to explain why the proposed changes are unsafe, unnecessary, or misaligned with project goals.

What is the best way to implement code-review changes without introducing errors?

The best way to implement code-review changes safely is to process feedback items one by one, evaluating technical correctness against the codebase first, and implementing each change alongside corresponding tests.

Can I use a structured workflow for code-review feedback from automated subagent reviewers?

Yes, a structured code-review feedback workflow works with both human partners and external subagent reviewers, maintaining project constraints by verifying every comment against the codebase before acting on automated suggestions.

When should I request clarification before implementing code-review feedback?

Request clarification on code-review feedback whenever incoming items are unclear, ambiguous, or potentially conflicting, ensuring you fully understand the requirement before verifying against the codebase and implementing changes.

Why does implementing code-review feedback directly lead to incorrectly applied changes?

Implementing code-review feedback directly causes errors because it skips verifying suggestions against the codebase, leading to ambiguous or incorrectly applied changes that lack technical reasoning and proper test coverage.