skills.rest
afonsoft
afonsoftCOMMUNITY
Explore all skills by this author →
Website𝕏@afonsoftGitHub

receiving-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation of code review feedback by enforcing a verify-before-implement workflow, eliminating performative agreement and unverified changes that can break a codebase. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with individual testing. - Source-Specific Handling: Differentiates trusted feedback from external reviewer suggestions, requiring technical verification and pushback when suggestions break functionality or violate YAGNI. - Use Case: A reviewer asks to remove legacy code; instead of agreeing immediately, you check build targets and backward compatibility, then push back with technical reasoning or implement with justification. ## Quick Start Use the receiving-code-review skill to evaluate and respond to the review comments on my current pull request.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How should I respond to code review feedback on a pull request?▼

Read all feedback completely, restate each requirement in your own words, verify it against the codebase, then implement one item at a time with individual testing. Avoid performative agreement like "great point" and use technical acknowledgment instead.

When should I push back on a code review suggestion?▼

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

What should I do when code review feedback is unclear?▼

Stop and ask for clarification before implementing anything. Partial understanding leads to wrong implementation, so clarify all unclear items first even if you understand the rest.

How do I handle external reviewer suggestions versus team feedback?▼

External suggestions require verification: check technical correctness, existing functionality impact, and full context before implementing. Trusted team feedback can be implemented after understanding, but still ask when scope is unclear.

What is the correct order for implementing multi-item review feedback?▼

Clarify unclear items first, then fix blocking issues like breaks and security problems, followed by simple fixes like typos, then complex refactoring. Test each fix individually and verify no regressions.

Related Skills

Explore More Software Engineering Skills→
brave-experimentsbrave-experiments
1

impl-review

Implement code review feedback on pull requests with automated validation.

Official
Advanced
CommunityToolkitCommunityToolkit
622

pr-review-response

Replies to GitHub PR review comment threads after fixing code via gh CLI and GraphQL.

Official
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
srbhrsrbhr
28.1k

receiving-code-review

Guide engineers through code-review feedback using a six-step response pattern.

Community
Basic