receiving-code-review

Enforces a six-step protocol for responding to code review feedback.

12|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ovargas/virtual-team --skill receiving-code-review-ovargas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ovargas/virtual-team/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/ovargas/virtual-team --skill receiving-code-review-ovargas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Process code review feedback by enforcing verify-before-implement discipline.

Core Features & Use Cases

  • Enforces a disciplined, step-by-step response to code reviews to prevent performative agreements.
  • Applies across PR reviews, inline comments, SDD reviewer agents, and founder feedback to ensure changes are properly validated.
  • Supports a repeatable workflow that reduces ambiguity and accelerates safe integration of feedback.

Quick Start

Provide a precise, technically grounded reply to reviews following the 6-step protocol.

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 without immediately implementing changes?

Process code review feedback by enforcing a verify-before-implement discipline using a six-step protocol: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This ensures rigorous validation of pull request comments before any code changes occur.

What is performative agreement in code reviews and how do I avoid it?

Performative agreement in code reviews happens when developers accept feedback without validation. Avoid it by applying a structured protocol that requires you to verify the technical accuracy of reviewer comments before responding or implementing changes.

What steps should I follow to respond to a pull request review rigorously?

Follow a six-step protocol for pull request reviews: READ the feedback, UNDERSTAND the intent, VERIFY the technical accuracy, EVALUATE the impact, RESPOND with technically grounded reasoning, and IMPLEMENT the validated changes safely.

Does this code review response process work for inline PR comments and SDD reviewer agents?

Yes, the verify-before-implement discipline applies across PR reviews, inline comments, SDD reviewer agents, and founder feedback. It enforces consistent validation regardless of the feedback source to ensure safe integration.

How do I evaluate technical feedback from founders before changing my code?

Evaluate founder feedback by applying the VERIFY and EVALUATE steps of the code review protocol. This requires technically validating the feedback against your codebase and assessing its impact before proceeding to respond or implement any changes.