receiving-code-review

Evaluate code review feedback with structured verification and YAGNI checks.

38|12|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/databrickslabs/coding-agents-databricks-apps --skill receiving-code-review-databrickslabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/databrickslabs/coding-agents-databricks-apps/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/databrickslabs/coding-agents-databricks-apps --skill receiving-code-review-databrickslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common pitfalls of mishandling code review feedback, including performative agreement without evaluation, blind implementation of unvetted suggestions, and partial execution of unclear feedback that leads to bugs and wasted development effort.

Core Features & Use Cases

  • Structured Feedback Evaluation: Follow a step-by-step process to read, understand, verify, and evaluate all code review feedback before taking action.
  • Scenario-Specific Guardrails: Tailored guidance for feedback from your human partner, external reviewers, and unclear multi-item feedback, including YAGNI checks to avoid unnecessary feature work.
  • Use Case: When an external reviewer suggests adding a metrics tracking endpoint, you can first grep the codebase to check if it is actually used, push back with technical reasoning if it is unused, or implement it correctly if it is required.

Quick Start

Use the receiving-code-review skill to evaluate the code review feedback on your current pull request before implementing any suggested 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 evaluate code review feedback before implementing changes?

Evaluate code review feedback by following a structured process to read, understand, verify, and validate suggestions before taking action. This prevents performative agreement and blind implementation of unvetted code changes.

What is the best way to handle unclear code review comments on a pull request?

Handle unclear code review comments by using clarification protocols to resolve ambiguity before coding. This prevents partial execution of feedback that leads to bugs and wasted development effort on your pull request.

When should I push back on code review suggestions from external reviewers?

Push back on code review suggestions when technical verification proves they are unnecessary or misaligned. Apply YAGNI validation to check if requested features are actually used before implementing external reviewer feedback.

How do I apply YAGNI checks to code review feedback?

Apply YAGNI checks by verifying whether suggested additions are actually needed in the codebase before implementation. Grep the codebase to confirm usage, then push back with technical reasoning if the requested feature is unused.

Can I use this for automated tool feedback on my developer workflow?

Yes, this works for developer workflows receiving feedback from human partners, external reviewers, or automated tools during pull request reviews. It provides scenario-specific guardrails tailored to each feedback source to maintain codebase quality.

Why does blind implementation of code review suggestions cause bugs?

Blind implementation of code review suggestions causes bugs by skipping technical verification of feedback. Performative agreement without evaluation leads to unvetted changes that violate architectural decisions and waste development effort.