skills.rest
haryelramalho
haryelramalhoCOMMUNITY
Explore all skills by this author →
Website𝕏@haryel_devGitHub

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated May 28, 2026
Search Tags:#testing#code review#feedback#verification#clarification#pushback
One-click install
npx skills add https://github.com/haryelramalho/skills --skill receiving-code-review-haryelramalho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/receiving-code-review
Command: npx skills add https://github.com/haryelramalho/skills --skill receiving-code-review-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receives code review feedback without blind agreement, helping you verify suggestions before changing code so you avoid incorrect or unnecessary edits.

Core Features & Use Cases

  • Technical Verification: Check feedback against the actual codebase before accepting it.
  • Clarification First: Pause and ask questions when review items are incomplete or ambiguous.
  • Reasoned Pushback: Push back on suggestions that break behavior, violate YAGNI, or conflict with known constraints.
  • Incremental Implementation: Apply changes one item at a time and test each fix to reduce regressions.
  • Use Case: A reviewer asks for several changes, but two are unclear and one seems technically wrong; this Skill helps you clarify the unclear items, validate the questionable one, and then implement only what is correct.

Quick Start

Use this skill to review the feedback you received, verify each point against the codebase, and respond with either a clear clarification request, a technical pushback, or a concise confirmation of the fix.

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 unclear code review feedback before changing my code?▼

Verify code review feedback by checking suggestions against the actual codebase before implementation. Ask clarifying questions for ambiguous items, validate technically questionable comments, and push back when suggestions break behavior or violate constraints.

What is the best way to push back on code review comments that seem technically wrong?▼

The best way to push back on code review comments is to provide reasoned technical validation. Check the suggestion against existing decisions and codebase behavior, then respond with a clear technical explanation if the change breaks behavior or violates YAGNI principles.

How do I handle code review feedback with multiple unclear or conflicting suggestions?▼

Handle conflicting code review feedback by processing items one at a time. Clarify ambiguous suggestions first, validate questionable ones against the codebase, and implement only verified changes incrementally to avoid unnecessary edits and regressions.

When should I ask for clarification on a code review comment instead of just making the change?▼

You should ask for clarification on a code review comment when the feedback is incomplete, ambiguous, or conflicts with known constraints. Pausing to verify suggestions prevents blind agreement and avoids incorrect or unnecessary edits to the codebase.

Does blindly accepting code review suggestions cause regressions?▼

Blindly accepting code review suggestions can cause regressions. Applying changes one item at a time and testing each fix individually reduces regression risk by ensuring only technically validated and verified modifications are implemented.

Can I reject a peer review suggestion if it violates YAGNI or existing decisions?▼

You can reject a peer review suggestion if it violates YAGNI or existing decisions. Reasoned pushback is necessary when feedback breaks behavior or conflicts with constraints, ensuring only correct and necessary changes are applied to the codebase.

Related Skills

Explore More Software Engineering Skills→
AEtherlight-aiAEtherlight-ai

protect

Annotate passing code with protection levels and update policy documents.

Official
Intermediate
ScivorScivor

qa-only

Execute report-only QA tests on a web application and generate a health score, screenshots, and reproducible steps.

Community
Advanced
hung-phanhung-phan

code-review

Analyze code review processes to identify areas for improvement.

Community
Advanced
SuperCorksSuperCorks

address-pr-comments

Fetch GitHub PR reviews via gh CLI and apply latest reviewer feedback.

Community
Advanced