receive-review

Verify code review feedback against requirements, tests, and codebase before implementing changes.

Updated Aug 23, 2026

Search Tags:#testing #feedback #verification #clarification #review #code-review

Ready to run

npx skills add https://github.com/mengdehong/opencode-dotfiles --skill receive-review-mengdehong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receive-review
Source: https://github.com/mengdehong/opencode-dotfiles/tree/main/skills/receive-review
Command: npx skills add https://github.com/mengdehong/opencode-dotfiles --skill receive-review-mengdehong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review feedback can be noisy or unsafe when accepted at face value. This skill enforces technical rigor by requiring restatement, verification, and deliberate pushback before making changes.

Core Features & Use Cases

Restate feedback: Clarifies intent and aligns expectations with the actual codebase.
Technical verification: Checks requirements, tests, and potential impact before acting.
Structured pushback: Provides reasoned, code-aware responses when feedback is unclear or risky.
Use Case: When a reviewer requests a risky refactor, restate the requirement, assess impact, and request additional tests before proceeding.

Quick Start

Restate the feedback succinctly, ask clarifying questions, verify with tests and codebase, and proceed only after confirmation.

Frequently Asked Questions about receive-review

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

FAQPage Schema

How do I handle ambiguous code review feedback before implementing changes?▼

Handling ambiguous code review feedback requires restating the reviewer's intent, asking clarifying questions, and verifying the impact against the codebase and tests before proceeding with any modifications.

What is the best way to push back on a risky refactor request in a pull request?▼

Pushing back on a risky refactor request involves providing structured, reasoned responses based on technical verification of the codebase and tests to justify why the proposed changes need further clarification.

Why should I verify code review comments instead of accepting them directly?▼

Verifying code review comments prevents the introduction of unsafe or noisy changes into the codebase, ensuring technical correctness by deliberately assessing requirements and potential impact rather than blind acceptance.

How do I check if review feedback aligns with my codebase and tests?▼

Checking review feedback alignment involves restating the requirement succinctly, performing technical verification against existing codebase logic, and ensuring all tests pass before confirming the requested changes.

Can I request additional tests when a reviewer asks for a risky code modification?▼

Yes, when a reviewer requests a risky modification, you can restate the requirement, assess the technical impact, and explicitly request additional tests to ensure the codebase remains stable before proceeding.