sp-receive-review

Validate code-review feedback against the codebase and implement changes with tests.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/leessju/claude-skills --skill sp-receive-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sp-receive-review
Source: https://github.com/leessju/claude-skills/tree/main/sp-receive-review
Command: npx skills add https://github.com/leessju/claude-skills --skill sp-receive-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When code-review feedback arrives, this protocol provides a disciplined, objective, and auditable approach to assess, respond to, and implement changes with a focus on technical correctness and proper sequencing.

Core Features & Use Cases

  • Validation-first feedback processing: read feedback without bias, restate requirements, verify alignment with the codebase, evaluate technical correctness, respond with justification, and implement changes with tests.
  • Clear interaction rules: disallow unhelpful phrases; provide explicit guidance for handling unclear feedback with STOP and ASK.
  • Use Case: In PR reviews, the receiver processes feedback, validates what is needed, and guides the developer through implementing changes in the correct order, with tests.

Quick Start

Follow the six-step receive-review protocol to process the latest code-review feedback and implement the validated changes.

Frequently Asked Questions about sp-receive-review

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

FAQPage Schema
How do I process code-review feedback and implement changes systematically?

Process code-review feedback using a six-step protocol: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This ensures you validate technical correctness against the codebase and implement changes with tests in an orderly, auditable sequence.

What should I do when code-review feedback is incomplete or unclear?

When code-review feedback is incomplete or unclear, use explicit STOP and ASK interaction rules to request clarification. The protocol enforces rejection or clarification rules to prevent implementing feedback that lacks sufficient technical detail or context.

How do I verify if code-review feedback is technically sound before implementing?

Verify code-review feedback by checking its alignment with the existing codebase and evaluating its technical correctness. During the VERIFY and EVALUATE steps, you assess the feedback objectively before responding with justification or proceeding to implementation.

Can I use this structured code-review workflow for automated reviewer inputs?

Yes, the protocol defines specific interaction protocols for both human and external reviewer inputs. You can process and technically validate automated code-review feedback by following the same six-step receive-review sequence.

What is the correct sequence for responding to PR review comments and writing tests?

The correct sequence for PR review comments is to read feedback, restate requirements, verify against the codebase, evaluate technical soundness, respond with justification, and finally implement changes alongside tests. This prevents premature coding before validation.