receiving-code-review

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

1|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/HarmAalbers/claude-requirements-framework --skill receiving-code-review-harmaalbers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/HarmAalbers/claude-requirements-framework/tree/main/plugins/requirements-framework/skills/receiving-code-review
Command: npx skills add https://github.com/HarmAalbers/claude-requirements-framework --skill receiving-code-review-harmaalbers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to performative agreement or blind implementation of suggestions that may be technically wrong for the codebase. This Skill enforces a disciplined response pattern: verify feedback against the actual codebase before implementing anything. ## 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 evaluation rules for feedback from a trusted human partner, external reviewers, and multi-agent review systems like code-reviewer or test-analyzer. - Pushback Guidance: Criteria and phrasing for rejecting suggestions that break functionality, violate YAGNI, or conflict with architectural decisions. - Use Case: After a multi-agent review flags several issues in a pull request, use this Skill to cross-reference findings, clarify unclear items, implement blocking fixes first, and push back on incorrect suggestions with technical reasoning. ## Quick Start Use 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 do I respond to code review feedback professionally?▼

Restate the technical requirement in your own words, verify it against the codebase, then implement or push back with reasoning. Avoid performative responses like "great point" and let actions or technical acknowledgment carry the response.

How to handle unclear code review comments before implementing?▼

Stop and ask for clarification before implementing anything when feedback is unclear. Items may be related, so partial understanding leads to wrong implementations; clarify all items first, then implement in priority order.

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

How do I handle feedback from automated multi-agent code review?▼

Cross-reference findings across agents, since overlapping flags raise priority, and weight findings by each agent's expertise. Treat agent output as suggestions to verify independently, not orders to follow blindly.

What order should I implement multiple code review fixes in?▼

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 occur.