receiving-code-review

Verify code review feedback against codebase context before implementing changes.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill receiving-code-review-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/workflow/receiving-code-review
Command: npx skills add https://github.com/ajsai47/holyclaude --skill receiving-code-review-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common pitfalls of mishandling code review feedback, such as performative agreement, blind implementation of incorrect suggestions, and partial execution of unclear requests that lead to broken code, wasted effort, and unnecessary feature bloat.

Core Features & Use Cases

  • Technical Verification First: Enforces checking all feedback against your codebase context, existing functionality, and compatibility requirements before making any changes.
  • Structured Handling for All Reviewers: Provides specific guidelines for feedback from your human team, external reviewers, and multi-item review lists, including YAGNI checks to avoid adding unused features.
  • Use Case: When an external reviewer suggests removing legacy code that supports older OS versions, this Skill guides you to verify the build target and backward compatibility requirements before deleting anything, rather than blindly following the suggestion.

Quick Start

Use the receiving-code-review skill to evaluate all incoming code review feedback for your active pull request, verifying each suggestion against your codebase context before implementing any changes.

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 without blindly implementing incorrect suggestions?

Handle code review feedback by enforcing technical verification of all suggestions against your codebase context and compatibility requirements before making any changes, preventing broken code and wasted developer effort.

What is the best way to evaluate pull request feedback from external reviewers?

Evaluate pull request feedback by applying YAGNI compliance checks to avoid feature bloat, verifying unclear suggestions against existing functionality, and providing reasoned pushback against contextually irrelevant requests.

How do I implement multiple fixes from a multi-item code review list?

Implement multi-item code review fixes through step-by-step execution of individually tested changes, verifying each suggestion against prior architectural decisions and existing functionality before applying it to the pull request.

When should I push back on code review suggestions regarding legacy code?

Push back on code review suggestions when feedback conflicts with prior architectural decisions or fails technical verification, such as blindly deleting legacy code without verifying backward compatibility requirements and build targets.

How do I check if a code review suggestion violates YAGNI principles?

Check if a code review suggestion violates YAGNI principles by verifying whether the proposed feature addition is currently required by existing functionality or if it introduces unnecessary feature bloat and unused code.

Can I use this approach for feedback from human collaborators as well as automated reviewers?

Yes, this approach applies to all code review scenarios including feedback from human collaborators, external reviewers, and multi-item review lists, ensuring rigorous technical evaluation across your entire developer workflow.