How does this skill handle unclear review comments?

It enforces a 'stop and clarify' policy, requiring full understanding of all feedback items before any changes are implemented to prevent partial or wrong fixes.

What is the implementation order for multi-item feedback?

It prioritizes blocking issues and security fixes first, followed by simple fixes like typos, and finally complex logic or refactoring.

Can Claude push back on my suggestions with this skill?

Yes. If a suggestion is technically incorrect, violates YAGNI principles, or conflicts with prior architectural decisions, Claude will provide reasoned technical pushback.

Why does this skill discourage saying 'thank you' during reviews?

The skill prioritizes technical action over social performance to maintain focus on code correctness and minimize noise in the development cycle.

Does this skill help with external PR reviewers?

Yes, it is specifically designed to be skeptical of external feedback, checking for compatibility and usage before making changes to your codebase.

Code Review Reception

Name: Code Review Reception
Author: franroa

byfranroa

Collaboration Tools

Implements a rigorous, verification-first approach to handling code review feedback by prioritizing technical correctness over performative agreement.

About

This skill equips Claude with a disciplined framework for processing code review feedback, ensuring that every suggestion is technically validated before implementation. By moving away from passive acceptance and performative politeness, it enforces a structured workflow of reading, understanding, verifying, and evaluating suggestions against the actual codebase reality. The skill is particularly effective at identifying YAGNI violations, maintaining architectural consistency, and providing reasoned technical pushback when external suggestions conflict with project requirements or human partner decisions.

Key Features

Requires full clarification of multi-item feedback before starting implementation
Enforces a verify-before-implement protocol to ensure technical soundness
0 GitHub stars
Flags YAGNI violations to prevent the addition of unused or 'professional' features
Eliminates performative language and unnecessary gratitude for objective rigor
Provides a structured framework for pushing back on incorrect or out-of-context feedback

Use Cases

Evaluating feedback from external reviewers who may lack internal project context
Preventing feature creep and maintaining minimalist architectural standards
Managing complex, multi-item code reviews where clarity is paramount

About

Key Features

Requires full clarification of multi-item feedback before starting implementation
Enforces a verify-before-implement protocol to ensure technical soundness
0 GitHub stars
Flags YAGNI violations to prevent the addition of unused or 'professional' features
Eliminates performative language and unnecessary gratitude for objective rigor
Provides a structured framework for pushing back on incorrect or out-of-context feedback

Use Cases

Evaluating feedback from external reviewers who may lack internal project context
Preventing feature creep and maintaining minimalist architectural standards
Managing complex, multi-item code reviews where clarity is paramount