skills.rest
stefanfaur
stefanfaurCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

1|Updated Feb 10, 2026
Search Tags:#code review#feedback#collaboration#pull request#verification#yagni#pushback
One-click install
npx skills add https://github.com/stefanfaur/roach-marketplace --skill receiving-code-review-stefanfaur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/stefanfaur/roach-marketplace/tree/main/roach/skills/receiving-code-review
Command: npx skills add https://github.com/stefanfaur/roach-marketplace --skill receiving-code-review-stefanfaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents blind implementation of code review feedback by enforcing verification, clarification, and reasoned pushback instead of performative agreement. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify, evaluate, respond, and implement feedback one item at a time with individual testing. - Source-Specific Handling: Applies different trust levels for feedback from your human partner versus external reviewers, including YAGNI checks for unused features. - Use Case: When a reviewer suggests removing legacy code, verify build targets and backward compatibility requirements first, then push back with technical reasoning if the suggestion breaks existing functionality. ## Quick Start Apply the receiving-code-review skill to evaluate and respond to the review comments on my latest 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 before implementing it?▼

Read the complete feedback, restate the requirement in your own words, verify it against the codebase, evaluate whether it is technically sound, then respond with technical acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

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

Stop and ask for clarification on all unclear items before implementing anything. Partial understanding leads to wrong implementation because feedback items may be related, so never implement the clear items first and ask later.

When is it appropriate to 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 rather than defensiveness.

How do I handle feedback from external reviewers versus my team lead?▼

Treat external feedback as suggestions to evaluate: check technical correctness, platform compatibility, and whether the reviewer understands full context. Feedback from your human partner is trusted but still warrants clarification questions when scope is unclear.

Why should I avoid saying thanks or giving praise in code review responses?▼

Performative agreement like "great point" or "you're absolutely right" adds no technical value and can precede blind implementation. State the fix factually or just make the change, letting the code itself demonstrate the feedback was heard.

Related Skills

Explore More Software Engineering Skills→
haojing8312haojing8312
154

receiving-code-review

Verify code review feedback before implementing changes in pull requests.

Community
Intermediate
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
takemi-ohamatakemi-ohama

resolve-pr-comments

Automates replying to and resolving completed PR comment threads via GitHub CLI/APIs without changing code.

Community
Intermediate