skills.rest
manuelbrandner85
manuelbrandner85COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluates code review feedback by verifying it against the codebase.

Updated Nov 23, 2025
Search Tags:#code review#pull request#refactoring#verification#technical rigor#yagni
One-click install
npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill receiving-code-review-manuelbrandner85
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/manuelbrandner85/Weltenbibliothekapp/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill receiving-code-review-manuelbrandner85

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 process of reading, understanding, and verifying feedback against the current codebase reality.
  • Strategic Pushback: Provides a framework for challenging technically questionable or context-unaware suggestions using reasoned arguments.
  • Use Case: When a reviewer suggests a complex refactor that violates YAGNI or breaks existing functionality, this skill guides you to verify the usage via grep and push back with technical evidence rather than accepting the suggestion blindly.

Quick Start

Use the receiving-code-review skill to evaluate the latest pull request feedback by verifying each item against the codebase and preparing a technical response.

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 code review feedback that suggests unnecessary refactoring?▼

Handle code review feedback by verifying the suggested refactoring against the current codebase to ensure it does not violate YAGNI or break existing functionality before implementing any changes.

What is the best way to push back on a pull request review comment?▼

The best way to push back on a pull request review comment is to use reasoned discourse and technical evidence, such as grep results, to validate architectural constraints rather than performative agreement.

How do I verify technical correctness when receiving code review suggestions?▼

Verify technical correctness by systematically reading, understanding, and checking external review feedback against your project requirements and existing architectural constraints before making modifications.

When should I challenge feedback during a code review?▼

You should challenge feedback during a code review when suggestions are technically questionable, context-unaware, or require validation against the actual codebase reality to prevent blind implementation.

Can I use this approach for complex pull request workflows with external reviewers?▼

Yes, you can use this systematic technical verification approach for pull request workflows where external suggestions require strict validation against current architectural constraints and project requirements.

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
LazyNinja435LazyNinja435
1

receiving-code-review

Evaluate and implement code review feedback with verification and pushback protocols.

Community
Intermediate
LuisSambranoLuisSambrano
7

code-review

Perform systematic code review and static analysis across multiple programming languages.

Community
Advanced
pantheon-orgpantheon-org
1

receiving-code-review

Verify code review feedback through a six-step workflow before implementation.

Official
Basic