receiving-code-review

Verify code review feedback against the codebase and respond with structured patterns.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to receiving and processing code review feedback, ensuring technical accuracy and minimizing miscommunication.

Core Features & Use Cases

  • Feedback Verification: Before implementing changes, verify feedback against the codebase.
  • Response Patterns: Defines a clear, technical response pattern for code review feedback.
  • Handling Unclear Feedback: Provides guidance on dealing with unclear feedback, emphasizing the importance of clarification.
  • Source-Specific Handling: Offers different handling strategies depending on the source of the feedback (e.g., human partner, external reviewer).
  • YAGNI Check: Encourages consideration of the "You Ain't Gonna Need It" principle for "professional" features.
  • Implementation Order: Suggests a structured approach to implementing multiple feedback items.
  • Pushback: Guidelines on when and how to push back on technically unsound feedback.
  • Acknowledging Correct Feedback: Offers a methodical way to acknowledge and implement correct feedback.
  • Gracefully Correcting Pushback: Instructions on how to acknowledge mistakes made during pushback.
  • Common Mistakes: Lists common mistakes in code review reception and their fixes.

Quick Start

Load the receiving-code-review skill and use it to process code review feedback.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle code review feedback systematically before implementing changes?

Systematically handling code review feedback involves verifying comments against the codebase before implementation. You apply structured response patterns prioritizing technical correctness over social comfort, clarifying unclear points, and evaluating requested features using the YAGNI principle.

What is the best way to respond to technically incorrect code review comments?

Responding to technically incorrect code review comments requires structured pushback based on codebase verification. You should clearly articulate the technical reasoning, and if your pushback is proven wrong, gracefully acknowledge the mistake and proceed with implementing the correct feedback.

How do I prioritize and implement multiple code review feedback items?

Implementing multiple code review feedback items requires following a structured implementation order. You should first verify each item against the codebase, prioritize technically sound suggestions, apply the YAGNI check to filter unnecessary features, and methodically acknowledge correct feedback before starting implementation.

How do I process code review feedback from different sources like automated tools versus human reviewers?

Processing code review feedback requires different handling strategies depending on the source. You should apply technical verification rigor uniformly to both human partner feedback and external reviewer comments, ensuring that technical correctness dictates implementation regardless of the reviewer's identity.

What are common mistakes when receiving code review feedback and how do I fix them?

Common mistakes in receiving code review feedback include prioritizing social comfort over technical accuracy and implementing changes without verifying against the codebase. You can fix these by applying structured verification patterns, requesting clarification for unclear feedback, and using technical rigor to validate all comments.