Why does this skill discourage saying 'thanks' or 'excellent point'?

To prevent performative agreement. In professional technical workflows, actions and verified fixes are more valuable than social pleasantries, ensuring the focus remains on code correctness.

When will Claude push back on a reviewer's suggestion?

Claude will push back with technical reasoning if a suggestion breaks functionality, violates YAGNI principles, is technically incorrect for the specific stack, or lacks necessary project context.

How does the skill handle unclear feedback?

It instructs Claude to stop and ask for clarification immediately. It forbids partial implementation of multi-step feedback to avoid errors caused by related but misunderstood items.

What is the recommended response pattern for new feedback?

The pattern follows six steps: Read the feedback fully, Understand by restating it, Verify against the codebase, Evaluate technical soundness, Respond with technical acknowledgment, and Implement one item at a time.

Technical Code Review Reception

Name: Technical Code Review Reception
Author: EricOo0

byEricOo0

•

협업 도구

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

소개

The Technical Code Review Reception skill optimizes how Claude interacts with human and automated feedback during the development lifecycle. Instead of defaulting to blind implementation or social pleasantries like 'You're absolutely right,' this skill enforces a strict protocol of technical verification. It requires Claude to restate requirements, verify suggestions against the actual codebase, and provide reasoned pushback when suggestions conflict with project architecture or YAGNI principles. This ensures higher code quality and prevents the introduction of unnecessary complexity or regressions caused by misunderstood feedback.

주요 기능

Automated YAGNI checks to prevent the implementation of unused or over-engineered features.
5 GitHub stars
Verification-first response pattern ensures technical accuracy before any code changes.
Context-aware handling distinguishes between trusted partner directions and external reviewer suggestions.
Structured multi-item implementation strategy that prioritizes blocking and security issues.
Eliminates performative agreement and unnecessary gratitude to keep communication professional and concise.

사용 사례

Verifying external contributor suggestions against specific project constraints and legacy requirements.
Ensuring architectural integrity when receiving 'standard' advice that may not apply to a specific domain.
Processing complex Pull Request feedback where multiple reviewers provide conflicting or vague suggestions.

소개

주요 기능

Automated YAGNI checks to prevent the implementation of unused or over-engineered features.
5 GitHub stars
Verification-first response pattern ensures technical accuracy before any code changes.
Context-aware handling distinguishes between trusted partner directions and external reviewer suggestions.
Structured multi-item implementation strategy that prioritizes blocking and security issues.
Eliminates performative agreement and unnecessary gratitude to keep communication professional and concise.

사용 사례

Verifying external contributor suggestions against specific project constraints and legacy requirements.
Ensuring architectural integrity when receiving 'standard' advice that may not apply to a specific domain.
Processing complex Pull Request feedback where multiple reviewers provide conflicting or vague suggestions.