skills.rest
farslab
farslabCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often triggers performative agreement or blind implementation, leading to broken code, wasted effort on unused features, and missed clarification on unclear items. This Skill enforces a verify-before-implement discipline when responding to reviewers. ## Core Features & Use Cases - Structured Response Pattern: Read, understand, verify against the codebase, evaluate, respond, then implement one item at a time with tests. - Source-Specific Handling: Different rules for trusted human partners versus external reviewers, including pushback guidance and YAGNI checks for unused features. - Use Case: A reviewer suggests removing legacy code. Instead of agreeing immediately, you check build targets, discover backward-compatibility constraints, and respond with technical reasoning or a clarifying question. ## Quick Start Use the receiving-code-review skill to help me respond to this pull request review feedback before implementing any changes.

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 full feedback, restate each requirement in your own words, verify it against the actual codebase, then implement one item at a time with tests. Avoid performative agreement like "great point" and never implement before verifying.

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

Stop and ask for clarification before implementing anything, even if other items are clear. Partial understanding leads to wrong implementations because feedback items are often related.

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 code or tests.

How do I handle external reviewer suggestions differently from my team lead's?▼

External feedback requires extra skepticism: verify correctness for your codebase, check platform compatibility, and confirm the reviewer understands full context. If it conflicts with your partner's prior decisions, discuss with them first.

How do I reply to inline review comments on GitHub pull requests?▼

Reply within the comment thread using the GitHub API endpoint for pull request comment replies, not as 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