receiving-code-review

Restate, verify, and implement code-review feedback incrementally with testable results.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/softbreezee/claw-os --skill receiving-code-review-softbreezee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/softbreezee/claw-os/tree/main/temp_skills/superpowers-main/skills/receiving-code-review
Command: npx skills add https://github.com/softbreezee/claw-os --skill receiving-code-review-softbreezee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often produce unclear or conflicting feedback. This Skill provides a disciplined approach to interpret, verify, and respond to review comments, ensuring changes are technically sound and aligned with the codebase.

Core Features & Use Cases

  • Clear restatement of reviewer intent to avoid misinterpretation
  • Technical verification against the actual codebase and tests
  • Incremental, testable implementation with justification for each change
  • Constructive pushback with technical reasoning when feedback is unclear or potentially harmful

Quick Start

Provide a code-review snippet and have the AI respond with a structured verification plan and an incremental implementation strategy.

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

To handle unclear code-review feedback, you can use a disciplined approach to restate the reviewer's intent, verify technical feasibility against the codebase, and implement changes incrementally with testable results.

What is the best way to verify technical feasibility before implementing code-review changes?

Verifying technical feasibility involves checking the proposed code-review changes against the actual codebase and existing tests to ensure the modifications are technically sound and correctly aligned with the repository structure.

How do I push back on code-review comments that seem technically risky?

To push back on risky code-review comments, provide constructive feedback with clear technical reasoning and justification, ensuring the response focuses on technical correctness rather than subjective disagreement.

Can I use this approach for incremental implementation of multiple code-review suggestions?

Yes, this approach supports incremental implementation by applying code-review changes step by step, allowing you to test each modification individually and provide technical justification for every change made.

When should I restate reviewer intent during a code review?

You should restate reviewer intent whenever code-review feedback is unclear or potentially conflicting, ensuring you accurately understand the requested changes before performing any technical verification or implementation.

Do I need to provide my codebase for automated code-review verification?

You need to provide a code-review snippet, which allows the system to generate a structured verification plan and an incremental implementation strategy based on the provided feedback and technical context.