receiving-code-review

Process code-review feedback with verification before implementing changes.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill receiving-code-review-oduffy-delphi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/oduffy-delphi/coordinator-claude/tree/main/plugins/coordinator/skills/receiving-code-review
Command: npx skills add https://github.com/oduffy-delphi/coordinator-claude --skill receiving-code-review-oduffy-delphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers often receive code-review feedback without a clear, verifiable path to safely implement changes.

Core Features & Use Cases

  • Structured reaction pattern: read, understand, verify, evaluate, respond, and implement.
  • Handles unclear items with triage and documented reasoning to prevent ambiguous changes.
  • Supports source-specific handling and pushback when feedback is technically questionable.

Quick Start

Process incoming code-review feedback by reading, restating the requirement, verifying against the codebase, evaluating its technical validity, responding with reasoned pushback, and implementing changes one item at a time.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I process code-review feedback safely before implementing changes?

Process code-review feedback safely by reading, restating the requirement, verifying against the codebase, evaluating technical validity, responding with reasoned pushback, and implementing changes one item at a time.

What is the best way to handle unclear code-review comments during a formal review cycle?

Handle unclear code-review comments with structured triage and documented reasoning to prevent ambiguous changes, ensuring feedback is verified against the codebase before any implementation begins.

How do I push back on technically questionable code-review feedback?

Push back on questionable code-review feedback by verifying the item against the codebase, evaluating its technical validity, and responding with rigorous, documented reasoning to support your decision.

Can I use a structured workflow for triage and documentation of code-review items across teams?

Yes, this structured workflow applies to formal review cycles across teams, handling unclear items with triage and documented reasoning to ensure technical rigor before implementing changes.

Why should I verify code-review feedback against the codebase before making changes?

Verifying code-review feedback against the codebase ensures technical rigor, prevents ambiguous changes, and provides a clear, repeatable path to safely implement requested modifications.