skills.rest
Berkay2002
Berkay2002COMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Verify and prioritize code review feedback before implementing changes.

Updated Aug 27, 2026
Search Tags:#feedback#github#verification#code-review#pull-request#technical-pushback
One-click install
npx skills add https://github.com/Berkay2002/skills --skill receiving-code-review-berkay2002
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Berkay2002/skills/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/Berkay2002/skills --skill receiving-code-review-berkay2002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid performative or blind acceptance of code review suggestions by enforcing verification, clarification, and technical rigor before implementation.

Core Features & Use Cases

  • Structured Response Pattern: Read, restate, verify, evaluate, respond, then implement one item at a time with tests.
  • Source-Specific Handling: Differentiate trusted human partner feedback from external reviewers and apply appropriate skepticism and checks.
  • Prioritization & Safety: Clarify unclear items first, prioritize blocking fixes, run YAGNI checks for requested features, and push back with technical reasoning when necessary.
  • Use Case: Responding to a GitHub PR with mixed inline comments where some suggestions may break compatibility or add unused features.

Quick Start

Restate the requested changes, ask clarifying questions for any unclear items, verify against the codebase, then implement fixes in prioritized order while testing each change.

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 that conflicts with existing architecture?▼

Handle conflicting code review feedback by verifying suggestions against the codebase, checking architectural context, and providing reasoned technical pushback instead of blind implementation.

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

The best way to respond to unclear pull request comments is to restate the requested changes, ask clarifying questions first, and prioritize blocking fixes before implementing.

How do I push back on technically questionable code review suggestions?▼

Push back on questionable code review suggestions by evaluating the feedback, running YAGNI checks for requested features, and responding with clear technical reasoning before making changes.

When should I differentiate between trusted partner feedback and external reviewer comments?▼

Differentiate between trusted partner and external reviewer feedback when applying skepticism and checks, ensuring source-specific handling to prevent performative acceptance of pull request changes.

How do I implement code review changes safely without breaking compatibility?▼

Implement code review changes safely by verifying feedback against the codebase, prioritizing the implementation order, and testing each change one item at a time to ensure compatibility.

Related Skills

Explore More Software Engineering Skills→
mymx2mymx2
4

gh-address-comments

Fetch and cluster unresolved GitHub pull request review threads and inline comments.

Community
Advanced
galangryandanagalangryandana
20

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Basic
Till-Crazy-Tears-Us-ApartTill-Crazy-Tears-Us-Apart
27

receiving-code-review

Validate incoming code review feedback against codebase reality and project standards.

Community
Intermediate
ybbms777ybbms777
1

lint

Run standardrb, erblint, and Brakeman checks on Ruby and ERB files.

Community
Intermediate