receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Updated Nov 8, 2024

Search Tags:#communication #verification #analysis #engineering #code-review #pull-request

Ready to run

npx skills add https://github.com/cqkxxc/cqkxxc.github.io --skill receiving-code-review-cqkxxc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handles code review feedback with technical rigor, ensuring you understand and verify requirements before implementing changes, rather than giving performative agreement or blindly applying suggestions.

Core Features & Use Cases

Structured feedback handling: Follow a repeatable pattern (READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT) to process each feedback item.
Risk-aware decision making: Push back with technical reasoning when feedback is unclear, unsafe, or misaligned with the codebase.
Consistent cross-review approach: Apply the same disciplined workflow across multiple PRs, reducing guesswork and drift.

Quick Start

Clarify every item by restating the requirement, verify it against the codebase, and implement changes one at a time with tests.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I process code review feedback without blindly applying suggestions?▼

Processing code review feedback safely requires a structured workflow: understand the requirement, verify it against your codebase, evaluate technical viability, and implement changes incrementally with tests rather than blindly applying suggestions.

What is the best way to handle unclear pull request feedback?▼

Handling unclear pull request feedback involves asking clarification questions and pushing back with technical reasoning when suggestions are unsafe or misaligned with the codebase, avoiding performative agreement.

How do I verify technical requirements from code review comments against my codebase?▼

Verifying technical requirements from code review comments requires restating the requirement, checking it against the actual codebase reality, and evaluating technical viability before making any incremental code changes.

Can I apply a consistent workflow to process multiple code reviews?▼

Yes, applying a consistent READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, and IMPLEMENT workflow across multiple pull requests reduces guesswork and drift when handling varying code review feedback.

When should I push back on code review suggestions?▼

You should push back on code review suggestions with technical reasoning when the feedback is unclear, unsafe, or misaligned with the actual codebase reality instead of giving performative agreement.

How do I implement code review changes safely after verification?▼

Implementing code review changes safely requires applying changes one item at a time with tests, ensuring each verified requirement is addressed incrementally rather than applying bulk modifications.