receiving-code-review

Verify code review feedback against codebase context before implementing fixes.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill receiving-code-review-yves-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/yves-s/just-ship/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/yves-s/just-ship --skill receiving-code-review-yves-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers avoid blind or performative acceptance of code review suggestions by enforcing a verification-first response pattern that reduces regressions and misimplementations.

Core Features & Use Cases

  • Structured Response Pattern: Read, restate, verify, evaluate, respond, then implement to ensure changes are correct for the codebase.
  • Source-Specific Handling: Distinguishes between trusted human partners and external reviewers and prescribes different verification and pushback steps.
  • Risk Prioritization & YAGNI Checks: Orders fixes by severity (blocking → simple → complex) and validates whether suggested features are actually used before implementing.
  • Use Case: Respond to inline GitHub review comments by clarifying unclear items, verifying technical correctness, and applying only verified fixes with tests.

Quick Start

Restate each reviewer request in your own words, verify it against the codebase, ask for clarification where unclear, then implement fixes one at a time starting with blocking issues.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I properly verify code review feedback before implementing changes?

Verify code review feedback by restating the reviewer's intent, checking it against your codebase context, and evaluating technical correctness before writing any code. This structured response pattern prevents blind acceptance of suggestions and reduces regressions.

What is the best way to handle GitHub pull request review comments systematically?

Handle pull request review comments by categorizing feedback from trusted partners versus external reviewers, prioritizing fixes by severity from blocking to simple, and prompting for clarification on unclear items before applying verified changes.

How do I push back on code review suggestions that violate YAGNI principles?

Push back on code review suggestions by validating whether requested features are actually needed before implementing them. Evaluate the technical rigor of the feedback against your codebase context and provide reasoned technical arguments for declining unnecessary additions.

Can I use a structured process to prioritize fixes from inline pull request reviews?

Yes, you can order fixes by severity, starting with blocking issues, then simple changes, and finally complex modifications. This risk prioritization ensures critical pull request feedback is addressed first while maintaining codebase stability.

Why should I restate the intent of code review comments before writing fixes?

Restating the intent of code review comments ensures you correctly understand the reviewer's goal before modifying production codebases. This verification step catches misinterpretations early, preventing misimplementations and reducing unnecessary regressions.

Does blindly accepting code review suggestions cause regressions in production codebases?

Blindly accepting code review suggestions causes regressions by bypassing codebase context verification. Applying a verification-first response pattern ensures changes are technically correct and appropriate for the production environment before implementation.