receiving-code-review

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

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SESELOVSKYDarian/Vase --skill receiving-code-review-seselovskydarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/SESELOVSKYDarian/Vase/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/SESELOVSKYDarian/Vase --skill receiving-code-review-seselovskydarian

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 ambiguous 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 individual testing. - Source-Specific Handling: Different rules for trusted human partner feedback versus external reviewer suggestions, including pushback criteria and YAGNI checks. - Use Case: A reviewer suggests removing legacy code and adding a metrics endpoint. Instead of agreeing, you check build targets for backward compatibility needs and grep the codebase to confirm the endpoint is actually called before implementing. ## Quick Start Use 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 items one at a time with individual testing. Avoid performative agreement phrases and push back with technical reasoning when a suggestion is wrong.

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 are often 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 by adding unused features, is technically incorrect for your stack, or conflicts with prior architectural decisions. Use technical reasoning and reference working code or tests.

Should I implement every suggestion from external reviewers?

No. Treat external feedback as suggestions to evaluate, not orders. Check whether each suggestion is technically correct for your codebase, breaks existing functionality, and whether the reviewer understands the full context before implementing.

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 rather than posting a top-level PR comment. This keeps the discussion attached to the specific code line being reviewed.