skills.rest
raybird
raybirdCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback against architectural constraints and project requirements.

1|Updated Jan 28, 2026
Search Tags:#software engineering#code review#pull request#refactoring#verification#technical rigor
One-click install
npx skills add https://github.com/raybird/telenexus --skill receiving-code-review-raybird
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/raybird/telenexus/tree/main/skills/tao-of-opencode/references/superpowers/receiving-code-review
Command: npx skills add https://github.com/raybird/telenexus --skill receiving-code-review-raybird

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents performative agreement and blind implementation of code review feedback, ensuring that all changes are technically verified and aligned with the codebase's actual requirements.

Core Features & Use Cases

  • Technical Verification: Enforces a strict protocol to validate feedback against codebase reality before implementation.
  • Strategic Pushback: Provides a framework for technically sound disagreement when suggestions break functionality or violate YAGNI principles.
  • Use Case: When an external reviewer suggests a complex refactor that seems unnecessary, use this skill to verify the actual usage of the code and push back with technical reasoning instead of blindly accepting the suggestion.

Quick Start

Apply the receiving code review protocol to evaluate the latest pull request feedback and determine which items require clarification versus immediate implementation.

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?▼

Evaluating code review feedback requires validating suggestions against codebase reality, architectural constraints, and YAGNI compliance before implementation. This prevents blind implementation by enforcing a strict technical verification protocol to ensure functional integrity.

When should I push back on a pull request code review suggestion?▼

Push back on pull request review suggestions when changes break functionality, violate YAGNI principles, or introduce unnecessary complexity. Use strategic pushback grounded in technical reasoning and codebase verification rather than performative agreement.

What is performative agreement in code reviews and how do I avoid it?▼

Performative agreement in code reviews is blindly accepting feedback without technical validation. Avoid it by verifying all suggested changes against actual code usage, architectural constraints, and project requirements to ensure technical correctness before applying them.

How do I verify if a refactoring suggestion violates YAGNI compliance?▼

Verify YAGNI compliance by checking the actual usage of the code targeted for refactoring. Validate whether the suggested changes are technically necessary for current requirements or introduce unnecessary complexity, enabling technically sound disagreement if needed.

Does this code review protocol work for external reviewer feedback?▼

Yes, the code review protocol applies to software development workflows where external or peer feedback must be validated. It ensures all code changes are verified for technical correctness and functional integrity before being applied to the codebase.

Related Skills

Explore More Software Engineering Skills→
chokky-educationchokky-education

receiving-code-review

Standardizes incoming code review feedback verification and technical response preparation for pull requests and peer sessions.

Community
Intermediate
git-towngit-town
3.4k

end-to-end-tests

Run Gherkin end-to-end tests via make and Cucumber for Go.

Official
Intermediate
cockroachdbcockroachdb
6.0k

code-review

Review Pebble code, PRs, and diffs for correctness issues.

Official
Basic
gaganpasupuletigaganpasupuleti

receiving-code-review

Verify code review feedback against codebase constraints before implementing changes.

Community
Intermediate