receiving-code-review

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

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/stefaniuk/loadout --skill receiving-code-review-stefaniuk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/stefaniuk/loadout/tree/main/.github/skills/receiving-code-review
Command: npx skills add https://github.com/stefaniuk/loadout --skill receiving-code-review-stefaniuk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Receiving code review feedback often leads to performative agreement, blind implementation of questionable suggestions, or partial fixes when items are unclear. This Skill enforces a verify-before-implement discipline so review feedback is evaluated against the actual codebase before any changes are made. ## 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. - Pushback Guidance: Provides technical reasoning patterns for rejecting incorrect suggestions and gracefully correcting your own wrong pushback. - 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 a technically grounded question before changing anything. ## Quick Start Ask the assistant to apply the receiving-code-review workflow to the latest pull request review comments before implementing any suggested 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 complete feedback, restate the requirement in your own words, verify it against the codebase, evaluate whether it is technically sound, then respond with a technical acknowledgment or reasoned pushback. Implement one item at a time and test each fix individually.

How do I handle unclear code review comments?▼

Stop and ask for clarification before implementing anything when any feedback item is unclear. Partial understanding leads to wrong implementations because items may be related, so clarify all ambiguous points first.

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 rather than being defensive.

Should I treat external reviewer feedback the same as my team lead's feedback?▼

No. Feedback from your human partner is trusted and implemented after understanding, while external reviewer feedback requires verification against the codebase first. If external feedback conflicts with your partner's prior decisions, stop and discuss it with them first.

What is the YAGNI check for code review suggestions?▼

When a reviewer suggests implementing a feature properly, search the codebase for actual usage first. If nothing calls the code, propose removing it instead of building it out; if it is used, then implement the suggestion properly.

How do I reply to inline GitHub review comments?▼

Reply within the comment thread using the GitHub API replies endpoint for that specific comment, not as a top-level PR comment. This keeps the discussion attached to the relevant line of code.