How does it handle external versus internal reviewers?

It applies a higher level of skepticism to external feedback, requiring checks for compatibility, version support, and whether the reviewer understands the full codebase context.

How does the skill handle unclear feedback?

It instructs Claude to stop implementation immediately and request specific clarification on unclear items to prevent partial or incorrect changes.

Why does this skill discourage saying 'thank you' or 'great point'?

This skill prioritizes technical action over social performance; the code itself serves as the acknowledgment of feedback. This avoids performative agreement and keeps communication focused on technical reality.

Does it always follow reviewer suggestions?

No, it encourages technical skepticism and pushback if a suggestion breaks functionality, lacks context, or violates YAGNI (You Ain't Gonna Need It) principles.

Receiving Code Review

Name: Receiving Code Review
Author: EricOo0

byEricOo0

•

Collaboration Tools

Processes code review feedback with technical rigor by prioritizing verification and clarity over performative agreement.

About

This skill optimizes how Claude handles code review feedback, ensuring that suggestions are technically validated against the current codebase before implementation. It enforces a strict response pattern that eliminates social filler and performative gratitude, focusing instead on technical verification, clarifying unclear requirements, and pushing back against suggestions that violate YAGNI principles or architectural decisions. It is particularly useful for maintaining high code quality while preventing the implementation of unnecessary or incorrect 'best practices' suggested by external sources.

Key Features

Context-aware pushback logic for technically questionable suggestions
Structured handling of unclear or multi-item feedback requests
6 GitHub stars
Automated YAGNI checks against the codebase for suggested features
Strict verification-first response pattern for all review feedback
Elimination of performative gratitude and social filler in communications

Use Cases

Clarifying ambiguous feedback before starting implementation
Handling PR feedback from human partners or external reviewers
Validating if suggested 'proper' features are actually necessary for the current project scope

About

Key Features

Context-aware pushback logic for technically questionable suggestions
Structured handling of unclear or multi-item feedback requests
6 GitHub stars
Automated YAGNI checks against the codebase for suggested features
Strict verification-first response pattern for all review feedback
Elimination of performative gratitude and social filler in communications

Use Cases

Clarifying ambiguous feedback before starting implementation
Handling PR feedback from human partners or external reviewers
Validating if suggested 'proper' features are actually necessary for the current project scope