receive-review

Process reviewer feedback through a structured repair workflow with verification gates.

2.6k|696|Updated Mar 12, 2026

Search Tags:#workflow #review #bugs #quality-assurance #code-review #pull-request

Ready to run

npx skills add https://github.com/zts212653/clowder-ai --skill receive-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receive-review
Source: https://github.com/zts212653/clowder-ai/tree/main/cat-cafe-skills/receive-review
Command: npx skills add https://github.com/zts212653/clowder-ai --skill receive-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Processing reviewer feedback is time-consuming and error-prone without a disciplined flow. It ensures the team interprets and acts on the feedback with proper technical justification, prioritization, and traceability.

Core Features & Use Cases

Classify feedback into code-level issues and vision-level concerns, then decide whether to patch or redesign.
Enforce a structured repair workflow (read, classify, clarify, verify, fix, confirm) to ensure traceability and quality.
Require explicit reviewer confirmation before merging, with clear documentation of Red→Green progress.

Quick Start

Review the latest feedback, run the repair workflow, and present a concise repair confirmation to the reviewer.

Frequently Asked Questions about receive-review

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

FAQPage Schema

How do I process code review feedback to fix pull request bugs systematically?▼

To process code review feedback systematically, this Skill enforces a structured repair workflow: reading, classifying, clarifying, verifying, fixing, and confirming fixes to drive pull requests from Red to Green with technical justification.

What is the best way to prioritize P1 and P2 issues in code review feedback?▼

The best way to prioritize P1 and P2 code review issues is to classify them into code-level defects and vision-level concerns, then determine whether to apply a targeted patch or execute a full redesign based on rigorous technical justification.

How do I enforce verification gates before merging code review fixes?▼

To enforce verification gates before merging, this workflow requires passing a spec gate, mechanism gate, and feature gate, documenting the Red to Green progress, and securing explicit reviewer confirmation.

When do I need to redesign versus patch code based on reviewer feedback?▼

You need to redesign rather than patch when reviewer feedback highlights vision-level concerns, whereas code-level defects typically require targeted fixes, ensuring both are justified technically before merging.

Does this code review repair workflow require explicit reviewer confirmation before merge?▼

Yes, this code review repair workflow requires explicit reviewer confirmation before merge, ensuring all P1 and P2 feedback is resolved, verification gates are passed, and Red to Green progress is clearly documented.