receiving-code-review

Evaluate code review feedback against codebase realities before implementation.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/vrazdalovschi/dotfiles --skill receiving-code-review-vrazdalovschi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/vrazdalovschi/dotfiles/tree/main/agents/skills/shared/receiving-code-review
Command: npx skills add https://github.com/vrazdalovschi/dotfiles --skill receiving-code-review-vrazdalovschi

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, preventing blind implementation of potentially incorrect or unnecessary suggestions.

Core Features & Use Cases

  • Technical Verification: Empowers users to critically assess code review suggestions before implementation.
  • Reasoned Pushback: Provides a framework for constructively challenging feedback that is unclear, technically unsound, or conflicts with project goals.
  • Structured Implementation: Guides the user on how to prioritize and implement feedback items systematically.
  • Use Case: When a reviewer suggests a change that seems to contradict existing architecture or introduces unused functionality, this skill helps you ask clarifying questions and push back with technical reasoning, rather than blindly accepting the suggestion.

Quick Start

When receiving code review feedback, verify each item against the codebase and respond with technical acknowledgment or reasoned pushback.

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?

Code review feedback requires technical evaluation against codebase realities and project context before any implementation. This process ensures only technically sound and relevant suggestions are applied, preventing performative agreement and incorrect modifications to the architecture.

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

Constructive pushback on code review comments involves using technical reasoning to challenge suggestions that are unclear or technically unsound. You must verify the feedback against existing architecture and project goals, then respond with clarifying questions rather than blind acceptance.

When should I not implement code review feedback directly?

You should not implement code review feedback directly when suggestions contradict existing architecture, introduce unused functionality, or lack technical soundness. Feedback must be rigorously verified against codebase realities and project context to prevent incorrect or unnecessary changes.

How do I prioritize and structure the implementation of code review feedback?

Structuring code review feedback implementation requires systematically evaluating and prioritizing each item. You must verify every suggestion against the codebase, assess its technical soundness, and then implement only the technically valid changes in a structured, prioritized manner.