skills.rest
OmniNode-ai
OmniNode-aiOFFICIAL
Explore all skills by this author →
GitHub

receiving-code-review

Verify code review feedback against codebase reality before implementation.

3|1|Updated Oct 9, 2025
Search Tags:#code review#feedback#verification#technical rigor#yagni#pushback
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill receiving-code-review-omninode-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/receiving-code-review
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill receiving-code-review-omninode-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you navigate code review feedback by ensuring technical rigor and verification before implementation, preventing performative agreement or blind acceptance of suggestions.

Core Features & Use Cases

  • Technical Verification: Empowers you to verify feedback against codebase reality before acting.
  • Reasoned Pushback: Facilitates constructive disagreement with technically unsound suggestions.
  • Use Case: When a reviewer suggests a change that seems to break existing functionality or is unnecessary according to YAGNI principles, this skill guides you to ask clarifying questions and push back with technical reasoning rather than blindly implementing.

Quick Start

When receiving code review feedback, verify each item technically before implementing any suggestions.

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

Evaluate code review feedback by verifying each suggestion technically against the codebase reality before acting. This ensures technical rigor and prevents blind acceptance of changes that might break functionality.

What is the best way to push back on code review comments?▼

Push back on code review comments by providing reasoned disagreement using technical reasoning and clarifying questions. This ensures pushback is based on technical correctness rather than performative agreement.

When should I reject code review suggestions based on YAGNI principles?▼

Reject code review suggestions based on YAGNI principles when a reviewer proposes a change that is technically unnecessary. Ask clarifying questions and push back with technical reasoning to avoid implementing unneeded features.

Why do I need to verify codebase reality when receiving code review feedback?▼

Verify codebase reality when receiving code review feedback to ensure technical correctness and maintainability. This verification prevents performative agreement and blind acceptance of unsound suggestions.

How to handle code review feedback that seems to break existing functionality?▼

Handle code review feedback that seems to break existing functionality by applying technical verification. Ask clarifying questions and push back with technical reasoning rather than blindly implementing the suggested changes.

Related Skills

Explore More Software Engineering Skills→
mezivillagermezivillager
1

receiving-code-review

Verify and evaluate code review feedback against codebase reality before implementation.

Community
Intermediate
tonombtonomb

resolving-merge-conflicts

Resolve git merge and rebase conflicts by analyzing commit history and reconciling code changes.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
mitchellfyimitchellfyi
3

dxprreview

Triage pull request review comments and implement scoped fixes.

Community
Advanced