What is performative agreement in code reviews?

Performative agreement refers to excessive praise or automatic validation (like saying 'Great catch!' or 'You're absolutely right!') instead of technically evaluating a suggestion. This skill replaces these responses with factual, evidence-based communication.

Can this skill help with scope creep?

Yes, it includes a YAGNI (You Ain't Gonna Need It) filter that prompts you to question suggestions that add unused features or unnecessary complexity to the current scope.

Why is the 'Restate Requirements' step important?

Restating the feedback in your own words ensures that you fully understand the reviewer's intent before implementation, preventing errors caused by misinterpretation.

How does this skill handle incorrect feedback?

It uses a technical push-back protocol where the AI provides specific technical reasons and evidence from the codebase to explain why a suggestion may be incorrect or harmful to the project.

Code Review Verification

Name: Code Review Verification
Author: bostonaholic

bybostonaholic

•

Collaboration Tools

Enforces a verification-first approach to code review feedback by evaluating suggestions rigorously and eliminating performative agreement.

About

The Receiving Code Review skill implements a disciplined protocol for processing feedback within the Research-Plan-Implement (RPI) framework. It ensures that Claude critically evaluates every suggestion rather than providing automatic, performative agreement. By following a structured response pattern—Read, Restate, Verify, Assess, and Respond—this skill ensures that code changes are technically justified, align with project patterns, and are properly tested. It also provides a clear framework for pushing back against incorrect suggestions or unnecessary complexity, maintaining the integrity of the codebase.

Key Features

Sequential implementation sequence prioritizing blocking issues
Standardized response patterns (Restate, Verify, Assess)
Verification-first feedback assessment protocol
2 GitHub stars
Structured push-back protocol for incorrect or out-of-scope suggestions
Elimination of performative agreement and excessive praise

Use Cases

Evaluating suggestions from external reviewers who lack project context
Filtering out unnecessary features using the YAGNI (You Ain't Gonna Need It) principle
Processing complex pull request feedback from senior developers

About

Key Features

Sequential implementation sequence prioritizing blocking issues
Standardized response patterns (Restate, Verify, Assess)
Verification-first feedback assessment protocol
2 GitHub stars
Structured push-back protocol for incorrect or out-of-scope suggestions
Elimination of performative agreement and excessive praise

Use Cases

Evaluating suggestions from external reviewers who lack project context
Filtering out unnecessary features using the YAGNI (You Ain't Gonna Need It) principle
Processing complex pull request feedback from senior developers