receiving-code-review

Evaluate code review feedback before implementing suggested changes.

1|Updated Mar 6, 2014
One-click install
npx skills add https://github.com/79yuuki/dotfiles --skill receiving-code-review-79yuuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/79yuuki/dotfiles/tree/main/claude/skills/receiving-code-review
Command: npx skills add https://github.com/79yuuki/dotfiles --skill receiving-code-review-79yuuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid blindly accepting code review feedback by providing a disciplined process for understanding, verifying, and responding to suggestions with technical accuracy.

Core Features & Use Cases

  • Feedback Evaluation Workflow: Guides developers through reading, understanding, verifying, and implementing review comments one item at a time.
  • Technical Pushback Guidance: Helps identify unclear, incorrect, unnecessary, or context-mismatched suggestions and respond with evidence-based reasoning.
  • Use Case: Apply this Skill when reviewing pull request comments, external reviewer suggestions, or architectural feedback that requires validation before changing code.

Quick Start

Ask the receiving-code-review skill to help evaluate these code review comments before making any changes.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
Do I need to validate all pull request comments before refactoring code?

Validating all pull request comments before refactoring ensures technical rigor in developer workflows. You must apply a feedback evaluation workflow to verify each item, clarifying unclear requirements and checking context before implementing any suggested changes.

How do I evaluate code review feedback before implementing changes?

Evaluating code review feedback requires a structured workflow to read, understand, and verify each pull request comment individually before implementation. This prevents blindly accepting suggestions by applying technical judgment and evidence-based reasoning to validate reviewer recommendations.

What is the best way to handle incorrect or unclear code review comments?

Handling incorrect code review comments involves technical pushback using evidence-based reasoning to identify context mismatches. You clarify unclear requirements and respond with technical accuracy rather than blindly implementing unverified suggestions from external reviewers.

How do I respond to pull request suggestions that seem unnecessary?

Responding to unnecessary pull request suggestions requires technical pushback guidance to identify and reject irrelevant changes. You validate the architectural context against the feedback, ensuring strict verification practices before accepting any code review recommendations.

When should I verify external reviewer suggestions during a code review?

You should verify external reviewer suggestions whenever architectural discussions or developer workflows require technical judgment. Applying structured verification prevents incorrect implementation by ensuring every feedback item is validated for technical accuracy before code changes.

Do I need to validate all pull request comments before refactoring code?

Validating all pull request comments before refactoring ensures technical rigor in developer workflows. You must apply a feedback evaluation workflow to verify each item, clarifying unclear requirements and checking context before implementing any suggested changes.