superpowers-receiving-code-review

Process code-review feedback through a six-step verification workflow.

Updated Dec 16, 2025

Search Tags:#workflow #quality-assurance #risk-management #code-review #guardrails #technical-verification

Ready to run

npx skills add https://github.com/fegome90-cmd/fork_agent --skill superpowers-receiving-code-review-fegome90-cmd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superpowers-receiving-code-review
Source: https://github.com/fegome90-cmd/fork_agent/tree/main/.kilocode/skills/superpowers-receiving-code-review
Command: npx skills add https://github.com/fegome90-cmd/fork_agent --skill superpowers-receiving-code-review-fegome90-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often produce ambiguous or emotionally charged feedback. This Skill enforces a technical, verification-first approach to understand requirements and verify changes before implementing.

Core Features & Use Cases

Six-step process: read, understand, verify, evaluate, respond, implement.
Per-item implementation: apply changes one at a time to minimize risk.
Guardrails & clarity: requires clarifications for unclear items and technical justification for each change.
Consistency across workflows: works with standard PR reviews and multi-review scenarios.

Quick Start

Process incoming code-review feedback by following the six-step method: read, understand, verify, evaluate, respond, and implement, applying changes one item at a time.

Frequently Asked Questions about superpowers-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 before implementing changes?▼

Handle code-review feedback by applying a six-step process: read, understand, verify, evaluate, respond, and implement. This enforces technical rigor and requires clarifications for ambiguous items before writing any code.

What is the best way to process code review comments to avoid performative agreement?▼

The best way to process code review comments is using a verification-first approach with per-item implementation. This requires technical justification for each change, applying them one at a time to minimize risk and prevent superficial agreement.

How do I verify technically questionable feedback during a PR review?▼

Verify technically questionable PR review feedback by enforcing a structured evaluation step before responding. This requires demanding technical justification and clarifications for questionable items, ensuring changes are validated before implementation.

Can I use a structured code review workflow for multi-review scenarios?▼

Yes, you can use a structured code review workflow for multi-review scenarios. The six-step process provides consistency across standard PR reviews and multiple-reviewer workflows, enforcing technical evaluation for every item.

Why do I need technical justification for each code-review change?▼

Technical justification for each code-review change is needed to enforce a verification-first approach. Guardrails require you to verify requirements and evaluate feedback before implementing, minimizing risk and avoiding performative agreement.

What are the limitations of using a per-item implementation approach for code reviews?▼

The limitation of per-item implementation is that it requires strict sequential execution of the six-step process for each piece of feedback. This enforces guardrails and minimizes risk, but may slow down workflows with high volumes of trivial comments.