receiving-code-review

Evaluate code review feedback against the codebase before implementation.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/darkmatter/skills --skill receiving-code-review-darkmatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/darkmatter/skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/darkmatter/skills --skill receiving-code-review-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you handle code review feedback with technical rigor instead of reflexive agreement, so you can avoid implementing unclear, incorrect, or conflicting suggestions.

Core Features & Use Cases

  • Feedback Verification: Checks whether review comments are technically correct for the current codebase before any changes are made.
  • Clarification First: Stops implementation when feedback is ambiguous or partially understood, preventing costly partial fixes.
  • Reasoned Pushback: Supports skeptical evaluation of external reviewer suggestions, especially when they break existing behavior or violate YAGNI.
  • Incremental Implementation: Encourages one change at a time with validation after each fix.
  • Use Case: A reviewer asks for a broad refactor and several bug fixes; this Skill helps you confirm what is actually needed, question weak suggestions, and then implement only the verified items.

Quick Start

Use the receiving-code-review skill to assess this review feedback, verify each point against the codebase, and tell me what to clarify, reject, or implement first.

Frequently Asked Questions about 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?

Verify code review feedback by evaluating each comment against the current codebase for technical correctness and scope before making any modifications. This prevents blind acceptance of incorrect suggestions and ensures changes are actually needed.

What is the best way to handle ambiguous pull request comments?

Handle ambiguous pull request comments by stopping implementation immediately and requesting clarification from the reviewer. This prevents costly partial fixes caused by acting on partially understood feedback.

How do I push back on incorrect code review suggestions on GitHub?

Push back on incorrect code review suggestions by applying reasoned evaluation to external reviewer feedback, especially when suggestions break existing behavior or violate YAGNI principles. Skeptical evaluation ensures technical rigor over reflexive agreement.

When should I reject code review feedback instead of implementing it?

Reject code review feedback when suggestions are technically incorrect for the current codebase, lack sufficient context, or introduce conflicting changes. Verification against the actual code helps identify which items to clarify, reject, or implement.

Can I implement multiple code review changes at once?

Implement code review changes one at a time with validation after each fix rather than batching them together. Incremental implementation ensures each accepted change is verified independently before moving to the next.