superpowers-receiving-code-review

What This Skill Does

The superpowers-receiving-code-review skill is designed to transition the AI from a passive assistant to a rigorous technical partner during code review cycles. It prioritizes objective technical accuracy over conversational pleasantries. By enforcing a structured, validation-first approach, the skill ensures that every piece of feedback is vetted against the existing codebase, local constraints, and architectural context before any modifications occur. It eliminates performative "yes-man" behavior—such as excessive thanking or empty agreement—in favor of technical clarity, precise refactoring, and logical pushback when feedback is found to be incorrect or harmful.

Installation

To integrate this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/axelhu/openclaw-receiving-code-review

Use Cases

• Senior Code Reviews: When managing complex pull requests where external reviewers may lack full context or provide suggestions that conflict with architectural goals.
• Refactoring & Optimization: Situations where reviewers suggest "best practice" changes that may violate YAGNI (You Ain't Gonna Need It) principles or introduce unnecessary bloat.
• Team Communication: Maintaining high-signal communication channels by focusing solely on technical requirements rather than social etiquette, ensuring PR discussions remain concise and actionable.
• Conflict Resolution: Providing a standard framework for justifying technical decisions when requested features threaten performance or existing stability.

Example Prompts

1. "I've received feedback suggesting we migrate our API handler to a microservice architecture. Analyze this against our current monolithic structure and tell me if this is a valid optimization or a violation of our current YAGNI constraints."
2. "Reviewer requested that I add logging to the helper module. Check if this module is currently utilized in the main execution path before implementing, and provide a technical justification if I should push back."
3. "Here is the feedback from the PR. Before you start, verify each point against our internal test suite and report which items are technically invalid or lack context."

Tips & Limitations

• Tone Adjustment: The skill intentionally suppresses "performative agreement." Do not be alarmed if the AI sounds clinical or blunt; this is by design to keep focus on code quality.
• Verification is Mandatory: The AI will refuse to implement changes it cannot verify. If you cannot provide sufficient context or local access for the AI to check the codebase, it will pause and ask clarifying questions.
• Sequential Implementation: The skill enforces a strict workflow: clarify, verify, and implement one change at a time. Do not attempt to force the AI to implement multiple, potentially conflicting review items simultaneously without full validation.