receiving-code-review

Clarify code-review feedback, verify it against the codebase, and implement changes incrementally.

10|4|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/HanHan666666/flutter-linglong-store --skill receiving-code-review-hanhan666666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/HanHan666666/flutter-linglong-store/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/HanHan666666/flutter-linglong-store --skill receiving-code-review-hanhan666666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often generate unclear or technically questionable feedback. This skill provides a disciplined approach to receiving and processing feedback to ensure changes are technically sound and verifiable.

Core Features & Use Cases

  • Clarify requirements: restate and confirm what is required before acting.
  • Verify against codebase: cross-check feedback with current implementation, tests, and architecture.
  • Incremental implementation: address feedback one item at a time, with focused verification and testing.
  • Use Case: when a reviewer asks to modify a function but the requirement is ambiguous, you restate and verify before coding.

Quick Start

Provide a structured response to a code-review comment, then implement changes one item at a time after validation.

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 ambiguous code review feedback on a pull request?

Handling ambiguous code review feedback requires restating and confirming the requirement before acting. You must cross-check the feedback against the current codebase and architecture to ensure the requested modifications are technically correct and within project constraints.

What is the best way to verify code review comments against an existing codebase?

Verifying code review comments against an existing codebase involves cross-checking the feedback with the current implementation, tests, and architecture. Apply changes only if technically correct, providing a reasoned justification for the decision to maintain code quality.

How to implement pull request changes one item at a time without regressions?

Implementing pull request changes without regressions requires addressing feedback one item at a time. After each incremental modification, run focused tests to verify the update and confirm no regressions before closing the review.

When should I reject code review feedback during technical verification?

You should reject code review feedback during technical verification if the requested change is technically incorrect or violates project constraints. Provide a reasoned justification explaining why the current implementation is valid and skip the modification.

Does processing code review feedback require running tests after each modification?

Processing code review feedback does require running tests after each modification. Incremental implementation demands focused verification after applying one item at a time to confirm no regressions exist before closing the pull request.