receiving-code-review

Verify code review feedback against codebase logic before implementing changes.

7|1|Updated Mar 15, 2017

Search Tags:#code review #pull request #refactoring #verification #technical rigor #yagni

Ready to run

npx skills add https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD --skill receiving-code-review-henquewl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD/tree/main/.opencode/skills/superpowers/skills/receiving-code-review
Command: npx skills add https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD --skill receiving-code-review-henquewl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative agreement and blind implementation during code reviews, ensuring that all feedback is technically verified against the codebase before any changes are made.

Core Features & Use Cases

Technical Verification: Enforces a strict protocol to evaluate feedback for technical correctness and architectural alignment before implementation.
Strategic Pushback: Provides a framework for questioning or rejecting suggestions that violate YAGNI, break existing functionality, or lack context.
Use Case: When a reviewer suggests a complex refactor that might break legacy compatibility, this skill guides you to verify the impact, push back with technical reasoning, and consult your human partner rather than blindly applying the change.

Quick Start

Use the receiving-code-review skill to analyze the latest pull request feedback and generate a verification plan before implementing any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I evaluate code review feedback before implementing changes?▼

To evaluate code review feedback, apply technical verification against the codebase to prevent unnecessary changes. This ensures architectural integrity by requiring systematic validation of all suggestions before implementation.

What is the best way to push back on a pull request review suggesting a complex refactor?▼

The best way to push back on a complex refactor is to use strategic pushback with technical reasoning. Verify the impact on legacy compatibility, check for YAGNI violations, and consult your human partner rather than blindly applying changes.

Why does performative agreement happen during code reviews and how can I prevent it?▼

Performative agreement happens when developers blindly implement suggestions without technical verification. Prevent it by enforcing a strict protocol to evaluate feedback for technical correctness and architectural alignment before making any code changes.

When do I need to verify code review suggestions against YAGNI principles?▼

You need to verify code review suggestions against YAGNI principles when feedback might introduce unnecessary features or break existing functionality. Apply this during collaborative software development to maintain architectural integrity and technical rigor.

How do I generate a verification plan for pull request feedback?▼

To generate a verification plan for pull request feedback, analyze the latest review comments and systematically verify each suggestion against current codebase logic and project requirements before implementing any changes.

Can I reject code review feedback that lacks context or breaks existing functionality?▼

Yes, you can reject code review feedback that breaks existing functionality or lacks context. Use a framework for questioning suggestions that violate YAGNI principles or fail technical verification against the codebase.