skills.rest
Syedyasir001
Syedyasir001COMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

Guides verification and implementation of code review feedback with technical rigor.

Updated Apr 17, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill receiving-code-review-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/receiving-code-review
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill receiving-code-review-syedyasir001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to performative agreement, blind implementation of questionable suggestions, or partial fixes when items are unclear. This Skill enforces a verify-before-implement workflow so review feedback is evaluated against the actual codebase before any changes are made. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, then implement feedback one item at a time with individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback criteria and YAGNI checks. - Use Case: A reviewer suggests removing legacy code or adding a metrics endpoint. Instead of agreeing immediately, you grep the codebase, discover the endpoint is unused or the legacy code is required for backward compatibility, and respond with technical reasoning. ## Quick Start Use the receiving-code-review skill to evaluate this pull request feedback before I implement any of the suggested 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 respond to code review feedback professionally?▼

Restate the technical requirement, verify it against the codebase, then implement or push back with technical reasoning. Avoid performative phrases like "You're absolutely right" or "Great point" and let the code changes demonstrate the response.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification on every unclear item before implementing anything. Partial understanding leads to wrong implementations because feedback items are often related, so clarify all items first.

When should I push back on code review suggestions?▼

Push back when a suggestion breaks existing functionality, violates YAGNI for unused features, is technically incorrect for the stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working tests or code.

Should I implement every external reviewer suggestion?▼

No. External feedback is a suggestion to evaluate, not an order. Check whether it is technically correct for this codebase, breaks existing functionality, and whether the reviewer understands the full context before implementing.

How do I reply to inline GitHub review comments?▼

Reply within the comment thread using the GitHub API endpoint for pull request comment replies rather than posting a top-level PR comment. This keeps the discussion attached to the specific code line being reviewed.

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

Provide structured, actionable feedback for code reviews and mentoring sessions.

Community
Advanced
NJX-njxNJX-njx
55

prepare-pr

Rebase GitHub pull requests onto main, fix review issues, and run build and test gates.

Community
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
summarybotngsummarybotng
2

code-review-quality

Conduct context-driven code reviews focusing on quality, testability, and maintainability.

Official
Advanced