skills.rest
corvo007
corvo007COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Validate code review feedback against the codebase before implementing changes.

793|52|Updated Nov 22, 2025
Search Tags:#debugging#communication#quality-assurance#code-review#decision-making#pull-request#technical-verification
One-click install
npx skills add https://github.com/corvo007/MioSub --skill receiving-code-review-corvo007
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/corvo007/MioSub/tree/main/.agent/skills/receiving-code-review
Command: npx skills add https://github.com/corvo007/MioSub --skill receiving-code-review-corvo007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often arrives with ambiguity or questionable technical implications, and teams need a disciplined approach to verify, clarify, and implement changes correctly.

Core Features & Use Cases

  • Raw pattern for handling feedback: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT, ensuring changes align with the codebase's reality.
  • Clarification-first approach: asks targeted questions and restates requirements before acting to avoid misinterpretation.
  • Guardrails against performative agreement: prevents blind implementations and reduces regression risk in PRs.

Quick Start

Start by restating the received feedback in your own words, then verify it against the codebase before proceeding with any changes.

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 ambiguous code review feedback on a pull request?▼

To handle ambiguous code review feedback, restate the comments in your own words and verify them against the codebase before acting. This clarification-first approach prevents misinterpretation and ensures technically sound changes during implementation.

What is the best way to evaluate technical feedback before making code changes?▼

Evaluating technical feedback involves a six-step workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. You verify the suggestions against your codebase's reality to prevent blind agreement and reduce regression risk.

How do I ask for clarifications when a reviewer's suggestion is technically questionable?▼

Ask for clarifications by restating the received feedback and posing targeted questions about the technical implications. This ensures you fully understand the requirements and validates the technical soundness before modifying any code.

Can I use a structured workflow to prevent performative agreement during code reviews?▼

Yes, you can use a structured workflow to prevent performative agreement by enforcing technical verification and evaluation stages. This guardrail stops blind implementations and ensures changes align with the codebase's reality.

What are the limitations of immediately implementing pull request comments without verification?▼

Immediately implementing pull request comments without verification introduces high regression risk and misinterpretation. Skipping the technical verification step leads to blind agreement and changes that may not align with the codebase's reality.

Related Skills

Explore More Software Engineering Skills→
awinogradovawinogradov
5

pr:resolve

Analyze pull request comments, apply code fixes, and reply to reviewers via GitHub API.

Community
Advanced
MacPhobosMacPhobos

mpm-postmortem

Analyze errors in scripts, skills, and agents to generate improvement suggestions and fixes.

Community
Intermediate
marktantongcomarktantongco

feature-research

Research features, technologies, and implementation approaches for technical decisions.

Community
Advanced
oscardlfroscardlfr
1

kdoc-audit

Audit KDoc coverage on Kotlin public APIs and report missing documentation.

Community
Intermediate