skills.rest
gaganpasupuleti
gaganpasupuletiCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Verify code review feedback against codebase constraints before implementing changes.

Updated Mar 22, 2026
Search Tags:#software engineering#quality assurance#code review#pull request#technical verification
One-click install
npx skills add https://github.com/gaganpasupuleti/Resume-Matcher --skill receiving-code-review-gaganpasupuleti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/gaganpasupuleti/Resume-Matcher/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/gaganpasupuleti/Resume-Matcher --skill receiving-code-review-gaganpasupuleti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents performative agreement and blind implementation of code review feedback, ensuring that all suggestions are technically verified against the codebase before any changes are made.

Core Features & Use Cases

  • Verification Workflow: Enforces a strict process of reading, understanding, verifying, and evaluating feedback before taking action.
  • Technical Pushback: Provides a framework for questioning or rejecting feedback that is technically incorrect, violates YAGNI principles, or breaks existing functionality.
  • Use Case: When a reviewer suggests a complex refactor that might break legacy compatibility, this skill guides you to verify the build requirements and push back with technical reasoning rather than simply agreeing.

Quick Start

Use the receiving-code-review skill to evaluate the latest pull request feedback and determine which items require clarification or technical pushback.

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?▼

Verifying code review feedback requires a structured framework that enforces reading, understanding, and validating suggestions against codebase constraints and architectural decisions before taking any implementation action.

What is the best way to push back on incorrect pull request feedback?▼

The best way to push back on pull request feedback is to apply technical reasoning, checking if the suggestion violates YAGNI principles or breaks existing functionality, and formally rejecting it with technical justification.

Why should I avoid performative agreement during technical code reviews?▼

Avoiding performative agreement during technical code reviews prevents blind implementation of suggestions, which can introduce regressions and break legacy compatibility without first validating the build requirements.

How do I evaluate code review suggestions for legacy compatibility issues?▼

Evaluating code review suggestions for legacy compatibility involves verifying the proposed refactor against existing build requirements and architectural decisions to ensure the change does not break current functionality.

When should I reject a complex refactor suggested in a code review?▼

You should reject a complex refactor suggested in a code review when technical verification proves it violates YAGNI principles, lacks necessary build requirements, or threatens to break existing legacy compatibility.

Related Skills

Explore More Software Engineering Skills→
ZESCODEZESCODE

ZES-receiving-code-review

Verifies incoming pull request feedback before implementing any code changes.

Community
Advanced
susomejiassusomejias
9

review-and-ship

Review branch changes, run targeted tests, and open pull requests.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
NagyViktNagyVikt
2

receiving-code-review

Evaluate code review feedback for technical correctness and architectural integrity.

Community
Intermediate