receiving-code-review

Restate, validate, and test code review suggestions before implementing them.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Kinshuk699/sEYEght --skill receiving-code-review-kinshuk699
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Kinshuk699/sEYEght/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/Kinshuk699/sEYEght --skill receiving-code-review-kinshuk699

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined, technical workflow for receiving and acting on code review feedback so developers avoid performative agreement, blind implementation, or incorrect changes caused by misunderstanding or unverified suggestions.

Core Features & Use Cases

  • Structured Response Pattern: Read feedback fully, restate requirements, verify against the codebase, evaluate technical correctness, respond with acknowledgement or reasoned pushback, then implement and test one item at a time.
  • Clarification & Pushback Guidance: When feedback is unclear or incorrect, prompts for clarifying questions and shows how to push back with technical reasoning rather than defensiveness.
  • Scope & YAGNI Checks: Encourages searching the codebase for actual usage before adding "professional" features and reconciling external suggestions with your human partner's decisions.
  • Use Case: Handling multi-item PR feedback where some items are ambiguous, some break functionality, and some suggest unused features.

Quick Start

When you receive a review comment, restate the requested change, verify it against the codebase, ask for clarification on unclear items, and then implement one tested fix at a time.

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

Handling code review feedback requires restating the requested change, verifying it against the codebase, evaluating regressions, asking clarifying questions, and implementing tested fixes one at a time.

What is the best way to respond to incorrect code review suggestions?

Respond to incorrect code review suggestions by providing reasoned technical pushback instead of defensive agreement, validating the proposed change against actual codebase reality, and verifying scope before implementation.

How do I avoid blindly implementing pull request feedback?

Avoid blindly implementing pull request feedback by restating requirements, checking the actual codebase for regressions, and verifying technical correctness before writing any code changes.

When should I push back on technical feedback during a code review?

Push back on technical feedback during a code review when suggestions are ambiguous, suggest unused features violating YAGNI, or break existing functionality, using clarifying questions to resolve incorrect items.

Does this code review workflow apply to multi-item pull request feedback?

This code review workflow applies to multi-item pull request feedback by processing ambiguous and incorrect suggestions individually, ensuring each verified change is implemented and tested sequentially.

How do I check if a code review suggestion violates YAGNI principles?

Check if a code review suggestion violates YAGNI principles by searching the codebase for actual usage before adding professional features, reconciling external suggestions with your project decisions.