receiving-code-review

Verify code review feedback against the codebase before implementation.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill receiving-code-review-lapaixkemsdortshlee-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/lapaixkemsdortshlee-svg/AyitiMarket/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/lapaixkemsdortshlee-svg/AyitiMarket --skill receiving-code-review-lapaixkemsdortshlee-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you respond to code review feedback with technical rigor instead of reflexive agreement, so you can avoid implementing bad suggestions or missing important clarifications.

Core Features & Use Cases

  • Feedback Verification: Checks review comments against the actual codebase before changes are made.
  • Clarification First: Prompts you to resolve unclear or incomplete items before touching code.
  • Reasoned Pushback: Supports technically grounded disagreement when feedback conflicts with context, compatibility, or YAGNI concerns.
  • Use Case: A reviewer asks for a refactor that breaks platform compatibility; this Skill helps you verify the constraint, explain the issue, and decide whether to proceed or push back.

Quick Start

Use the receiving-code-review skill to evaluate the feedback, verify each item against the codebase, and respond with clarification, acceptance, or technical pushback before implementing 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 verify code review feedback before implementing changes?

Verify code review feedback by checking review comments against the actual codebase to ensure suggestions are technically valid. This process requires technical verification of constraints, compatibility, and existing decisions before modifying code to avoid implementing bad suggestions.

What is the best way to handle unclear GitHub pull request comments?

Handling unclear GitHub pull request comments requires resolving ambiguous items through clarification first. Instead of guessing the intent, you prompt for clarification to resolve incomplete feedback before touching any code in your software engineering workflow.

Can I push back on code review feedback that conflicts with my codebase?

You can push back on code review feedback when it conflicts with your codebase context. Reasoned pushback supports technically grounded disagreement for suggestions that break platform compatibility or violate YAGNI concerns, ensuring you do not blindly agree to bad refactors.

How do I respond to a code review suggestion that breaks platform compatibility?

Respond to a code review suggestion that breaks platform compatibility by verifying the constraint, explaining the issue, and deciding whether to proceed or push back. This ensures your response supports reasoned acknowledgment based on actual technical limitations.

When should I ask for clarification on a pull request review?

Ask for clarification on a pull request review when feedback is unclear, incomplete, or technically questionable. Clarification first is required to resolve ambiguous items before implementation, ensuring you only apply verified changes to the codebase.