skills.rest
MoofonLi
MoofonLiCOMMUNITY
Explore all skills by this author →
GitHub

receiving-code-review

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

2|Updated Jul 11, 2026
Search Tags:#code review#feedback#pull request#github#verification#yagni#pushback
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill receiving-code-review-moofonli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/receiving-code-review
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill receiving-code-review-moofonli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? 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 asks you to remove legacy code. Instead of agreeing immediately, you check build targets, discover backward-compatibility constraints, and respond with technical reasoning before changing anything. ## Quick Start Apply 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 as a developer?▼

Read all feedback completely, 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 instead show the fix in code.

How do I handle unclear code review comments?▼

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

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 architectural decisions. Use technical reasoning and reference working tests rather than being defensive.

Should I implement every suggestion from external reviewers?▼

No. Verify external feedback against your codebase first: check if it breaks functionality, whether the reviewer has full context, and if it works across all platforms. If you cannot verify, state the limitation and ask for direction.

What order should I implement multi-item review feedback in?▼

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

Related Skills

Explore More Software Engineering Skills→
maxjuniorbrmaxjuniorbr
2

code-review-excellence

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

Community
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
summarybotngsummarybotng
2

code-review-quality

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

Official
Advanced