skills.rest
ZESCODE
ZESCODECOMMUNITY
Explore all skills by this author →
GitHub

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Updated Jul 8, 2026
Search Tags:#quality assurance#code review#pull request#refactoring#yagni#technical verification
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-receiving-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ZES-receiving-code-review
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/ZES-receiving-code-review
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-receiving-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Verification Protocol: Enforces a strict sequence of reading, understanding, and verifying feedback against current codebase reality.
  • Technical Pushback: Provides a framework for challenging technically unsound or context-blind suggestions using objective reasoning.
  • Use Case: When an external reviewer suggests a refactor that breaks existing functionality or violates YAGNI principles, this skill guides the agent to push back with evidence rather than blindly accepting the suggestion.

Quick Start

Use the ZES-receiving-code-review skill to process the latest pull request feedback by verifying each item against the current codebase before implementation.

Frequently Asked Questions about ZES-receiving-code-review

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

FAQPage Schema
How do I verify code review feedback before implementing changes?▼

To verify code review feedback, enforce a strict sequence of reading, understanding, and validating each suggestion against the current codebase reality to ensure technical correctness before modifying any code.

What is the best way to push back on technically unsound pull request comments?▼

Push back on technically unsound pull request comments by using an objective reasoning framework to challenge context-blind suggestions, prioritizing evidence from existing system constraints rather than performative agreement.

How do I prevent blind implementation of code suggestions that violate YAGNI principles?▼

Prevent blind implementation of code suggestions violating YAGNI principles by systematically validating each refactoring request against architectural alignment and current system constraints before applying the changes.

Does this code review approach stop performative agreement during technical verification?▼

Yes, this code review approach stops performative agreement by requiring systematic validation of every external code suggestion against the codebase, ensuring technical pushback is structured and objective.

When should I challenge a refactoring suggestion from an external reviewer?▼

Challenge a refactoring suggestion from an external reviewer when it breaks existing functionality, violates YAGNI principles, or fails technical verification against current system constraints.

Related Skills

Explore More Software Engineering Skills→
51hhh51hhh

receiving-code-review

Evaluate code review feedback against the codebase before implementing changes.

Community
Intermediate
heyallencaoheyallencao
118

test-first

Generate failing tests upfront and iteratively develop code to pass them.

Community
Intermediate
LetPeopleWorkLetPeopleWork
16

engineering-standards

Detect SOLID, DRY, YAGNI, and KISS violations with refactoring guidance.

Official
Basic
chijunzhengchijunzheng

code-review

Review code across languages for defects, standards, and technical debt.

Community
Advanced