receiving-code-review

Clarify code-review feedback by verifying requirements against the codebase.

7|1|Updated Feb 1, 2026

Search Tags:#feedback #communication #verification #pushback #code-review #technical-rigor

Ready to run

npx skills add https://github.com/cloudfieldcz/cf-powers --skill receiving-code-review-cloudfieldcz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often arrives as vague or technically questionable guidance. This skill provides a disciplined approach to understand, verify, and act only on well-grounded requirements.

Core Features & Use Cases

Restate and clarify requirements to avoid misinterpretation.
Verify feedback against the actual codebase and project constraints.
Provide reasoned pushback with technical justification when feedback is incorrect or incomplete.

Quick Start

Ask clarifying questions and verify requirements before acting on feedback.

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 vague code review feedback before implementing changes?▼

Handle vague code review feedback by restating the requirements and asking clarifying questions to verify the guidance against the actual codebase before proceeding with any implementation.

What is the best way to push back on technically incorrect code review comments?▼

Push back on incorrect code review comments by verifying the feedback against project constraints and providing reasoned technical justification that aligns with the codebase reality before making changes.

How do I verify conflicting code review suggestions against the codebase?▼

Verify conflicting code review suggestions by applying a verification approach that checks the feedback against actual codebase constraints and restates the requirements to ensure alignment.

When should I ask clarifying questions during a code review?▼

Ask clarifying questions during a code review whenever feedback is unclear, technically questionable, or conflicts with existing requirements to ensure changes align with codebase reality.

Can I restate code review requirements to avoid misinterpretation?▼

Yes, you can and should restate code review requirements to avoid misinterpretation, providing technical justification and verifying the feedback against the codebase before acting on suggestions.