receiving-code-review

Evaluates code review feedback with technical verification before implementing suggested changes.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/xegheplimo-web/hermes-ops --skill receiving-code-review-xegheplimo-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/xegheplimo-web/hermes-ops/tree/main/skills/software-development/execution-discipline/receiving-code-review
Command: npx skills add https://github.com/xegheplimo-web/hermes-ops --skill receiving-code-review-xegheplimo-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback often gets implemented blindly or met with performative agreement, leading to broken functionality, wasted effort on unused features, and unchallenged incorrect suggestions. This Skill enforces a verify-before-implement discipline when responding to review comments from humans or automated reviewers like Codex and CodeRabbit. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate technical soundness, then respond with acknowledgment or reasoned pushback before implementing one item at a time. - Source-Specific Handling: Distinguishes trusted human feedback from external reviewer suggestions, applying extra verification checks for automated review tools. - YAGNI Validation: Greps the codebase for actual usage before implementing "proper" solutions, avoiding work on unused endpoints or features. - Use Case: When Codex or CodeRabbit flags an issue on a Devin-authored PR, the agent verifies the suggestion against the actual codebase, pushes back with technical reasoning if incorrect, and only converts agreed findings into implementation tasks. ## Quick Start Apply the receiving-code-review discipline to evaluate the latest review comments on this pull request before making any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How should I respond to code review feedback before implementing it?

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, evaluate whether it is technically sound for this project, then respond with acknowledgment or reasoned pushback. Implement one item at a time with tests.

How do I handle automated code review comments from Codex or CodeRabbit?

Verify each suggestion against the actual codebase before implementing: check technical correctness, whether it breaks existing functionality, and whether the reviewer understands full context. Push back with technical reasoning if the suggestion is wrong.

When should I push back on a code review suggestion?

Push back when a suggestion breaks existing functionality, the reviewer lacks full context, it violates YAGNI by building unused features, it is technically incorrect for the stack, or it conflicts with prior architectural decisions. Use technical reasoning, not defensiveness.

What is the YAGNI check in code review responses?

When a reviewer suggests implementing something properly, grep the codebase for actual usage first. If the code is unused, propose removing it instead of investing in a proper implementation; if it is used, proceed with the full fix.

How does this integrate with the Hermes review pipeline?

Codex review findings are classified as AGREE, PARTIAL, or DISAGREE by reconcile_review.py. Only AGREE findings become implementation tasks for Devin; DISAGREE findings represent architectural pushback and are never converted into tasks.