skills.rest
wsxwj123
wsxwj123COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Clarify and verify code review feedback against the codebase before implementation.

7|Updated Jan 27, 2026
Search Tags:#workflow#development#feedback#verification#pushback#code-review#technical-rigor
One-click install
npx skills add https://github.com/wsxwj123/opencode-skills-backup --skill receiving-code-review-wsxwj123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/wsxwj123/opencode-skills-backup/tree/main/receiving-code-review
Command: npx skills add https://github.com/wsxwj123/opencode-skills-backup --skill receiving-code-review-wsxwj123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Core Features & Use Cases

  • Establish a structured response pattern that separates understanding from action
  • Verify feedback against the codebase reality before making changes
  • Use case: when feedback is vague or conflicting, this process ensures changes are technically sound

Quick Start

Ask clarifying questions for any unclear items and verify each feedback item against the codebase before implementing.

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 code review feedback before implementing changes?▼

Handle code review feedback by clarifying and summarizing it before making codebase changes. You must verify each suggestion against actual project constraints to ensure technical correctness rather than blindly implementing it.

What is the best way to verify technically questionable code review comments?▼

To verify questionable code review comments, evaluate them against your codebase reality and technical constraints. Ask clarifying questions for vague items to ensure your response maintains technical rigor instead of performative agreement.

How do I structure my workflow when responding to conflicting code review suggestions?▼

Structure your workflow by following a six-step response pattern: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This process separates understanding from action to safely implement changes when facing conflicting feedback.

When should I ask clarifying questions about code review feedback?▼

Ask clarifying questions whenever code review feedback seems vague, unclear, or conflicting. Doing this before implementing suggestions ensures that subsequent codebase changes are technically sound and safely aligned with project reality.

Why should I verify code review feedback against the codebase?▼

Verify feedback against the codebase to ensure technical correctness and prevent unsafe modifications. This verification step checks each item against actual project reality and constraints before any development action is taken.

Related Skills

Explore More Software Engineering Skills→
lapaixkemsdortshlee-svglapaixkemsdortshlee-svg

receiving-code-review

Verify code review feedback against the codebase before implementation.

Community
Intermediate
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic
keshavraj936keshavraj936

lint-and-validate

Lint and statically analyze Node.js and Python code modifications.

Community
Intermediate
NovaAI-innovationNovaAI-innovation

code-review

Analyze Python code for linting errors and style guide adherence.

Community
Intermediate