receiving-code-review

Name: receiving-code-review
Availability: InStock
Author: xianmingyao

Restates feedback requirements and verifies them against the codebase before implementing changes.

1|1|Updated Mar 18, 2026

Search Tags:#workflow #verification #clarification #pushback #code-review #pull-request

Ready to run

npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill receiving-code-review-xianmingyao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/xianmingyao/openclaw-CaySon/tree/main/.agent/skills/receiving-code-review
Command: npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill receiving-code-review-xianmingyao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receiving code review feedback often leads to misinterpretation, premature changes, or blind agreement. This Skill enforces a rigorous, repeatable process that verifies requirements against the codebase before implementing changes.

Core Features & Use Cases

Read and restate feedback requirements to avoid misinterpretation.
Verify feedback against the current codebase and tests before implementing.
Push back with technical reasoning when feedback is unclear or incorrect.
Handle ambiguous items by requesting clarifications before proceeding.

Quick Start

Begin by reading the feedback in full, restating the requirement in your own words, and then verifying it against the codebase before proceeding with any implementation.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I handle unclear code review feedback before making changes?▼

Handle unclear code review feedback by restating the requirement in your own words and verifying it against the current codebase. Request clarification for ambiguous items before proceeding with any implementation to avoid misinterpretation.

What is the best way to push back on technically incorrect code review comments?▼

The best way to push back on technically incorrect code review comments is to verify the suggestion against the code reality first, then respond with clear technical reasoning. Avoid performative agreement and ensure your evaluation is deterministic.

How do I verify code review suggestions against the current codebase?▼

Verify code review suggestions by reading the feedback in full, understanding the intent, and checking the suggestion against the existing codebase and tests. Evaluate the technical validity before responding or implementing any incremental changes.

What steps should I follow when receiving pull request feedback?▼

When receiving pull request feedback, follow a deterministic workflow: read, understand, verify, evaluate, respond, and implement incrementally. This enforces test coverage and prevents premature changes or blind agreement with the reviewer.

When should I request clarification during a code review?▼

Request clarification during a code review when feedback is ambiguous or cannot be verified against the current codebase. Restate the requirement to confirm understanding and ask for specifics before proceeding with any implementation.

Can I apply this rigorous code review workflow to any software development process?▼

Yes, you can apply this code review workflow to any software development process where engineers must verify requirements against code reality. It enforces a repeatable process of restating, verifying, and evaluating feedback before implementation.