team-receiving-review-feedback

Evaluate review feedback through a six-step protocol before implementation.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/davekim917/bootstrap --skill team-receiving-review-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-receiving-review-feedback
Source: https://github.com/davekim917/bootstrap/tree/main/plugins/workflow/skills/team-receiving-review-feedback
Command: npx skills add https://github.com/davekim917/bootstrap --skill team-receiving-review-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined protocol to evaluate feedback before acting, reducing blind compliance and ensuring technical soundness.

Core Features & Use Cases

  • Structured 6-step review protocol (READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT) to transform feedback into verifiable actions.
  • Decision guardrails for agreeing, deferring, or disagreeing with reviewer input across PRs, design reviews, QA findings, and external reviews.
  • Audit-ready rationale and traceability during code reviews, architecture discussions, and process improvements.

Quick Start

When you receive a reviewer comment, apply the 6-step protocol to evaluate and respond before implementing.

Frequently Asked Questions about team-receiving-review-feedback

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 before implementing changes, apply a structured 6-step protocol: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This enforces technical soundness and prevents blind compliance with reviewer suggestions.

What is the best way to handle unclear reviewer comments on a pull request?

The best way to handle unclear reviewer comments is to use a hard gate mechanism that stops implementation until the feedback is fully clarified. This ensures you never act on ambiguous suggestions during code reviews.

How do I ensure technical soundness when responding to QA findings or design reviews?

Ensure technical soundness by applying decision guardrails to QA findings and design reviews. This process requires you to verify, evaluate, and document rationale before choosing to agree, defer, or disagree with the reviewer input.

Can I generate audit-ready rationale for code review decisions?

Yes, you can generate audit-ready rationale by enforcing a structured evaluation protocol during code reviews. This provides traceability for architecture discussions and process improvements by documenting the technical evaluation of each feedback item.

How do I prevent unsafe or biased decisions when acting on external reviewer suggestions?

Prevent unsafe or biased decisions by applying built-in safety checks before implementing external reviewer suggestions. This rigorous evaluation process verifies technical soundness and blocks biased or unsafe compliance across software projects.

When do I need a structured process for evaluating team workflow feedback?

You need a structured process for evaluating team workflow feedback when you want to reduce blind compliance and ensure technical soundness. It transforms feedback into verifiable actions across code reviews, design reviews, and QA findings.