receiving-code-review

Verify code review feedback against the codebase before implementing changes.

3|Updated Jan 22, 2026

Search Tags:#debugging #verification #clarification #best-practices #quality-assurance #code-review #pull-request

One-click install

npx skills add https://github.com/falconnt/windsurf-skills --skill receiving-code-review-falconnt

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/falconnt/windsurf-skills/tree/main/receiving-code-review
Command: npx skills add https://github.com/falconnt/windsurf-skills --skill receiving-code-review-falconnt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often arrives ambiguously or without verification, leading to implementation mistakes or wasted effort. This Skill guides you to interpret feedback accurately, ask clarifying questions, verify requirements against the codebase, and implement changes only after thorough validation.

Core Features & Use Cases

Clarify first: restate the requirement in your own words or request specifics when feedback is unclear.
Technical verification: compare feedback against the code, tests, and project constraints.
Incremental changes: apply feedback one item at a time, with focused verification and testing.
Risk mitigation: push back with technical reasoning when a proposed change risks regressions or deviates from project goals.

Quick Start

When you receive code review feedback, restate the requirement, ask for clarification if needed, verify against the repository, and implement items iteratively.

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I handle unclear code review feedback on a pull request?▼

Verify code review feedback by comparing suggestions against the code, tests, and project constraints before applying changes. This ensures technical correctness and prevents regressions.

What is the best way to push back on a code review suggestion?▼

The best way to push back on code review suggestions is by providing technical reasoning. Evaluate if the change risks regressions or deviates from project goals before responding.

How do I implement code review changes incrementally?▼

Use code review feedback on pull requests, inline comments, and review threads across any project. The process applies universally to interpret and validate feedback before changes are applied.

Why should I verify code review comments before modifying code?▼

Verify code review comments before modifying code to prevent implementation mistakes and wasted effort. Technical verification enforces quality assurance by confirming suggestions are correct.