skills.rest
acho1833
acho1833COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Evaluate code review feedback against the codebase before implementation.

Updated Dec 22, 2025
Search Tags:#code review#feedback#pull request#verification#clarification#pushback
One-click install
npx skills add https://github.com/acho1833/spreadline2 --skill receiving-code-review-acho1833
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/acho1833/spreadline2/tree/main/.claude/commands/receiving-code-review
Command: npx skills add https://github.com/acho1833/spreadline2 --skill receiving-code-review-acho1833

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you respond to code review feedback with technical rigor instead of reflexive agreement, reducing the risk of implementing unclear, incorrect, or harmful suggestions.

Core Features & Use Cases

  • Feedback Verification: Check review comments against the actual codebase before making changes.
  • Clarification Handling: Pause and ask questions when a review item is ambiguous or incomplete.
  • Reasoned Pushback: Push back on suggestions that break existing behavior, conflict with project context, or violate YAGNI.
  • Example Use Case: A reviewer asks for a broad refactor, but the implementation is unclear and may be unnecessary; this Skill guides you to verify the issue, identify missing context, and respond with a precise technical answer.

Quick Start

Use the receiving-code-review skill to help me evaluate this review feedback, identify anything unclear, and draft a technically sound response before I change the code.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code review feedback before implementing changes?▼

To evaluate code review feedback, verify comments against the actual codebase, clarify ambiguous items, and apply reasoned pushback against suggestions that break existing behavior or violate YAGNI. This prevents blind acceptance of technically questionable pull request changes.

What is the best way to respond to unclear pull request comments?▼

The best way to handle unclear pull request comments is to pause and ask clarification questions. Identifying missing context and responding with a precise technical answer prevents implementing broad refactors that may be unnecessary or harmful to the codebase.

When should I push back on code review suggestions?▼

You should push back on code review suggestions when they conflict with project constraints, break existing behavior, or violate YAGNI. Reasoned pushback ensures you apply technical rigor instead of reflexive agreement to external reviewer feedback.

Can I verify external reviewer feedback against my existing codebase?▼

Yes, you can verify external reviewer feedback by carefully comparing the suggestions against your actual codebase. This verification process checks correctness, scope, and existing behavior before you implement any inline comments or pull request changes.

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

Implementing code review feedback without verification causes problems because reflexive agreement risks applying unclear, incorrect, or harmful suggestions. Evaluating feedback first ensures changes align with project context and do not break existing functionality.

Related Skills

Explore More Software Engineering Skills→
yves-syves-s
24

receiving-code-review

Verify code review feedback against codebase context before implementing fixes.

Community
Intermediate
ilamanovilamanov

brief

Generate a one-pager summary of pull request changes with code tour.

Community
Intermediate
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
haryelramalhoharyelramalho

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Intermediate