receiving-code-review

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

Analyze and verify code review feedback for technical accuracy before implementation.

Updated Feb 27, 2026

Search Tags:#code review #feedback #implementation #verification #technical rigor #pushback

Ready to run

npx skills add https://github.com/ZJUxjy/opencode_lite --skill receiving-code-review-zjuxjy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/ZJUxjy/opencode_lite/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/ZJUxjy/opencode_lite --skill receiving-code-review-zjuxjy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically sound and relevant to the codebase before implementation, preventing unnecessary work and potential regressions.

Core Features & Use Cases

Technical Verification: Evaluates feedback against codebase reality, technical correctness, and existing functionality.
Reasoned Pushback: Provides a framework for constructively challenging feedback that is unclear, incorrect, or conflicts with project goals.
Structured Implementation: Guides the order of implementation for multiple feedback items, prioritizing critical fixes.
Use Case: When a reviewer suggests a change, this Skill helps you verify its necessity and correctness, ask clarifying questions if needed, and push back with technical reasoning if the suggestion is flawed, rather than blindly accepting it.

Quick Start

Use the receiving-code-review skill to evaluate feedback from an external reviewer on the latest pull request.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I verify code review feedback before implementing changes?▼

Verify code review feedback by evaluating it against codebase reality, technical correctness, and existing functionality. This prevents unnecessary work and regressions from flawed suggestions.

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

Push back on incorrect code review suggestions by providing reasoned arguments based on codebase context, existing functionality, and project goals. Constructively challenge flawed suggestions rather than blindly accepting them.

How do I prioritize multiple code review feedback items for implementation?▼

Prioritize multiple code review feedback items by structuring the implementation order based on technical criticality. Address critical fixes first to ensure efficient handling of valid suggestions.

When should I ask for clarification on code review feedback?▼

Ask for clarification on code review feedback when suggestions are unclear, questionable, or lack sufficient context. Prompting for clarification ensures you understand the technical intent before implementing changes.

Why does implementing code review feedback without verification cause regressions?▼

Implementing code review feedback without verification causes regressions because suggestions may conflict with existing functionality or project goals. Evaluating technical accuracy first prevents unnecessary work from flawed recommendations.