receiving-code-review

Evaluate code-review feedback against the codebase before implementing changes.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/atxinsky/skills --skill receiving-code-review-atxinsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/atxinsky/skills/tree/main/receiving-code-review
Command: npx skills add https://github.com/atxinsky/skills --skill receiving-code-review-atxinsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code-review feedback can be ambiguous or technically questionable. This Skill provides a rigorous, repeatable approach to interpreting feedback, validating it against the codebase, and guiding safe, incremental implementation.

Core Features & Use Cases

  • Structured six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT to ensure thorough understanding before acting.
  • Clarity handling: if any feedback items are unclear, STOP and request clarification with specific questions.
  • Technical verification: cross-check feedback against the repository's current state to avoid regressions.
  • Safe progression: implement changes one item at a time, with focused tests after each step.
  • Source-aware guidance: adjusts behavior when feedback comes from external reviewers vs. your human partner (trust but verify).

Quick Start

Provide the code-review feedback you received (paste the comments). The Skill will restate the requirements, check compatibility with the codebase, assess technical soundness, decide whether to push back or proceed, and guide you through implementing changes one at a time with verification after each step.

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?

To evaluate code-review feedback, restate the requirements, verify comments against the codebase, assess technical soundness, and implement changes incrementally. This process enforces disciplined engineering reasoning to catch ambiguous or risky suggestions before any code is modified.

What should I do when code review comments are unclear or conflicting?

When code review comments are unclear or conflicting, stop and request clarification with specific questions. This clarity-handling step prevents regressions by ensuring you fully understand the feedback before attempting any technical verification or implementation.

How do I verify if a code review suggestion will cause a regression?

To verify if a code review suggestion causes a regression, cross-check the feedback against the repository's current state. Technical verification ensures proposed changes are compatible with the existing codebase before you proceed with safe, incremental implementation.

What is the best way to handle technically questionable code review feedback?

The best way to handle questionable code review feedback is to apply technical evaluation and decide whether to push back or proceed. Assess the technical soundness of each comment against your codebase, then guide safe changes one item at a time with focused tests.

Can I use a structured workflow to process code review comments from external reviewers?

Yes, you can process code review comments from external reviewers using a structured workflow that applies source-aware guidance. The system adjusts behavior for external feedback versus internal partner comments, applying a trust-but-verify approach to ensure engineering rigor.