review-feedback

Name: review-feedback
Availability: InStock
Author: raddue

Verify code review feedback against codebase context before implementing changes.

10|2|Updated Feb 23, 2026

Search Tags:#code review #feedback #YAGNI #verification #technical rigor #pushback

Ready to run

npx skills add https://github.com/raddue/crucible --skill review-feedback-raddue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-feedback
Source: https://github.com/raddue/crucible/tree/main/skills/review-feedback
Command: npx skills add https://github.com/raddue/crucible --skill review-feedback-raddue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code review feedback is handled with technical rigor, preventing performative agreement and blind implementation, and promoting verification before action.

Core Features & Use Cases

Technical Verification: Empowers agents to verify feedback against codebase reality before implementing.
Reasoned Pushback: Facilitates constructive disagreement with feedback when technically unsound.
Clarity Seeking: Guides agents to ask clarifying questions for ambiguous feedback.
Use Case: When a reviewer suggests a change that seems incorrect or unnecessary, this skill helps the agent to investigate, ask targeted questions, and push back with evidence, rather than blindly accepting the suggestion.

Quick Start

Use the review-feedback skill to handle incoming code review comments by verifying them technically before implementing.

Frequently Asked Questions about review-feedback

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

FAQPage Schema

How do I handle code review feedback without blindly implementing changes?▼

Handle code review feedback by prioritizing technical verification and reasoned pushback over performative agreement. Verify suggestions against codebase context, check for regressions, and apply YAGNI principles before implementing changes one item at a time.

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

Push back on incorrect code review comments by investigating the feedback against codebase reality, asking targeted clarifying questions for ambiguous points, and responding with technical evidence rather than performative agreement.

How do I verify if a code review suggestion is technically sound?▼

Verify code review suggestions by scrutinizing them against codebase context, evaluating potential regressions, and applying YAGNI principles to ensure the feedback is technically necessary and understood before implementation.

When should I ask clarifying questions about code review feedback?▼

Ask clarifying questions about code review feedback when comments are ambiguous or seem technically unsound. This ensures the feedback is fully understood and prevents blind implementation of unnecessary changes that could introduce regressions.

Can I process multiple code review comments at once?▼

Process code review feedback one item at a time to ensure technical rigor. This approach prevents performative agreement and guarantees each suggestion is verified against the codebase and understood correctly before moving to the next.

Why does implementing code review feedback blindly cause problems?▼

Implementing code review feedback blindly causes problems by skipping technical verification, risking potential regressions, and violating YAGNI principles. Reasoned pushback ensures only technically sound changes are applied to the codebase.