receiving-code-review

Evaluate and respond to code review feedback with verification and prioritized implementation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid performative agreement and premature changes by providing a verification-first approach to receiving code review feedback, ensuring technical correctness and preventing regressions.

Core Features & Use Cases

  • Verification-first workflow: Follow the READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT steps to avoid blind implementation.
  • Clarification and pushback guidance: Formulate concise restatements, clarifying questions, or reasoned technical objections when feedback is unclear or incorrect.
  • Prioritization and testing: Recommend implementation order (blocking fixes, simple fixes, complex refactors) and testing each change individually to prevent regressions.
  • Use Case: When a PR receives multi-item feedback from an external reviewer, use this Skill to check technical correctness, ask for missing context, and implement verified fixes one at a time.

Quick Start

Draft a concise reply that restates understood items, asks for clarification on unclear items, and lists the verification steps you will run before implementing changes.

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 without blindly implementing changes?

To respond to code review feedback safely, follow a verification-first workflow: READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT. This prevents performative agreement and ensures technical correctness before altering any code.

What is the best way to handle unclear comments on a pull request?

Handle unclear pull request comments by formulating concise restatements and asking clarifying questions. This verification-first approach helps you gather missing context from the reviewer before proceeding with any code modifications.

How do I push back on incorrect code review feedback technically?

Push back on incorrect code review feedback by providing reasoned technical objections. Evaluate the reviewer's comments, run technical checks to verify the claims, and formulate a clear, technically rigorous response explaining the issue.

What order should I implement code review fixes to prevent regressions?

Implement code review fixes in the order of blocking fixes, simple fixes, and complex refactors. To prevent regressions effectively, test each individual change separately as you progress through the pull request review cycle.

Can I use this verification workflow for external reviewer feedback on multi-item PRs?

Yes, you can use this verification workflow for multi-item feedback from both external and internal reviewers. It helps check technical correctness, ask for missing context, and implement verified fixes one at a time.