What is performative agreement in AI code reviews?

Performative agreement occurs when an AI agent reflexively agrees with reviewer feedback using phrases like 'You're absolutely right!' without verifying if the suggestion is technically sound for the specific codebase.

Does this skill work with external reviewers?

Yes, it includes a specific 'External Reviewer' handling logic that applies skepticism and checks for platform compatibility and versioning before implementing changes.

Why are gratitude expressions like 'Thank you' forbidden?

The protocol prioritizes actions over words. By removing social niceties, the workflow maintains technical rigor and ensures that the response focus remains entirely on the implementation facts.

How does this skill handle ambiguous feedback?

The protocol requires the AI to stop all implementation and ask for clarification if even a single item in a list of suggestions is unclear, preventing partial or incorrect updates.

When will Claude push back on a suggestion?

Claude will push back using technical reasoning if a suggestion breaks existing functionality, lacks context, violates YAGNI, or conflicts with established architectural decisions.

Code Review Reception Protocol

Acerca de

The Code Review Reception skill transforms how Claude interacts with feedback by prioritizing technical rigor over social politeness. Instead of reflexively agreeing with reviewers, this skill mandates a 'verify-before-implementing' pattern that requires Claude to restate requirements, check the codebase for technical feasibility, and push back on suggestions that violate YAGNI principles or architectural decisions. It is particularly useful for maintaining code integrity in complex repositories where external feedback might lack full context or where 'professional' feature bloat needs to be strictly controlled.

Características Principales

Technical verification workflow (Read, Understand, Verify, Evaluate, Respond, Implement)
Automated YAGNI (You Ain't Gonna Need It) validation against codebase usage
17 GitHub stars
Strict elimination of performative agreement and social fillers
Structured handling for multi-item and ambiguous feedback sets
Conflict resolution logic for architectural and human-partner decisions

Casos de Uso

Pruning unnecessary feature suggestions through codebase grepping and usage analysis
Processing high-stakes feedback from external senior reviewers
Managing complex code migrations where backward compatibility is critical

Acerca de

Características Principales

Technical verification workflow (Read, Understand, Verify, Evaluate, Respond, Implement)
Automated YAGNI (You Ain't Gonna Need It) validation against codebase usage
17 GitHub stars
Strict elimination of performative agreement and social fillers
Structured handling for multi-item and ambiguous feedback sets
Conflict resolution logic for architectural and human-partner decisions

Casos de Uso

Pruning unnecessary feature suggestions through codebase grepping and usage analysis
Processing high-stakes feedback from external senior reviewers
Managing complex code migrations where backward compatibility is critical