receiving-code-review

Evaluate code review feedback against codebase constraints and the YAGNI principle.

19|5|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/Nir-Bhay/markups --skill receiving-code-review-nir-bhay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Nir-Bhay/markups/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/Nir-Bhay/markups --skill receiving-code-review-nir-bhay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically evaluated and verified against the codebase's reality, rather than being blindly or performatively accepted, preventing incorrect implementations and wasted effort.

Core Features & Use Cases

  • Structured Response Pattern: Guides the user through a systematic process of understanding, verifying, and responding to feedback.
  • Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback.
  • External Reviewer Scrutiny: Emphasizes a skeptical yet thorough approach to feedback from external sources.
  • YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle to avoid unnecessary feature creep.
  • Use Case: When a reviewer suggests a change, you follow the pattern: understand, verify against the codebase, evaluate technical soundness, and then respond with reasoned acknowledgment or pushback, implementing only after verification.

Quick Start

When receiving code review feedback, first understand the requirement, then verify its technical soundness against the codebase before responding or implementing.

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 against existing codebase constraints?

Evaluate code review feedback by systematically understanding the requirement, verifying its technical soundness against the codebase, and checking architectural decisions to prevent incorrect implementations and wasted effort.

What is the best way to handle ambiguous feedback from external code reviewers?

Handle ambiguous feedback from external reviewers by seeking clarification through structured communication before implementing any changes, ensuring the technical evaluation aligns with actual codebase reality rather than performatively accepting suggestions.

How do I apply the YAGNI principle when responding to code review suggestions?

Apply the YAGNI principle during code review evaluation by filtering out unnecessary feature creep, verifying technical relevance, and implementing changes only after confirming the suggestion is strictly necessary for current requirements.

Can I push back on code review feedback if it violates architectural decisions?

Yes, you can push back on code review feedback by providing a reasoned response after verifying the suggestion violates existing architectural decisions or codebase constraints, ensuring technical rigor over permissive implementation.

What steps should I follow before implementing changes requested in a code review?

Before implementing changes requested in a code review, follow a structured response pattern: understand the feedback, verify technical soundness against the codebase, evaluate relevance, and then respond with reasoned acknowledgment or pushback.