Why does this skill forbid saying 'Thank you' in reviews?

The core principle is technical correctness over social comfort. It prioritizes factual acknowledgments and code-based actions over performative politeness.

Can Claude push back on human suggestions with this skill?

Yes. If a suggestion is technically incorrect, breaks functionality, or violates YAGNI principles, Claude will provide a reasoned technical pushback instead of blind implementation.

How does this skill change Claude's response to feedback?

It removes performative phrases like 'You're absolutely right!' and forces Claude to verify suggestions against the current codebase before implementing changes.

How does the skill handle unclear instructions?

Claude is instructed to stop and ask for clarification on all ambiguous items before starting any work, preventing partial or incorrect implementations.

Code Review Reception

Name: Code Review Reception
Author: abudhahir

byabudhahir

•

Collaboration Tools

Processes code review feedback with technical rigor, prioritizing codebase verification over performative agreement.

About

This skill transforms how Claude interacts with code reviews by enforcing a strictly technical and analytical approach. It prevents the AI from blindly accepting suggestions or using overly polite 'performative' language, instead requiring it to verify feedback against the actual codebase, ask for clarification when requirements are ambiguous, and push back with technical reasoning if a suggestion is incorrect or violates YAGNI principles. It is an essential utility for maintaining high code quality and ensuring that implementations are driven by technical reality rather than social comfort.

Key Features

Eliminates performative agreement and filler language in favor of technical action
Handles ambiguous feedback by pausing for clarification on specific items
Applies YAGNI (You Ain't Gonna Need It) checks to evaluate the necessity of suggestions
1 GitHub stars
Enforces a strict verification-before-implementation workflow to prevent regressions
Provides standardized response patterns for GitHub PR threads and human partners

Use Cases

Managing complex, multi-item feedback lists where some items are unclear
Processing feedback from senior developers or external security reviewers
Responding to GitHub Pull Request comments with technical precision

About

Key Features

Eliminates performative agreement and filler language in favor of technical action
Handles ambiguous feedback by pausing for clarification on specific items
Applies YAGNI (You Ain't Gonna Need It) checks to evaluate the necessity of suggestions
1 GitHub stars
Enforces a strict verification-before-implementation workflow to prevent regressions
Provides standardized response patterns for GitHub PR threads and human partners

Use Cases

Managing complex, multi-item feedback lists where some items are unclear
Processing feedback from senior developers or external security reviewers
Responding to GitHub Pull Request comments with technical precision