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

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

How does the skill handle unclear instructions?

If feedback is ambiguous, the skill mandates a 'stop and clarify' approach. It prevents partial implementations that might be invalidated once the full context of the feedback is understood.

What is the 'Response Pattern' used by this skill?

It follows a six-step process: Read feedback, Understand (restate), Verify against codebase, Evaluate technical soundness, Respond with acknowledgment or pushback, and Implement/test one item at a time.

Why does this skill discourage saying 'Thank you' or 'You're right'?

This skill prioritizes technical action over social performance. By removing performative agreement, Claude focuses on demonstrating understanding through code implementation and technical verification.

Technical Code Review Reception

Name: Technical Code Review Reception
Author: Krosebrook

byKrosebrook

•

Collaboration Tools

Establishes a rigorous framework for processing code review feedback based on technical verification rather than performative agreement.

This skill optimizes how Claude interacts during the code review process by prioritizing technical integrity over social compliance. It implements a structured 'Read-Verify-Evaluate' response pattern that ensures suggestions are technically sound for the specific codebase before implementation. By eliminating performative fillers and 'thank you' loops, the skill focuses Claude on action-oriented results, YAGNI (You Ain't Gonna Need It) checks, and the ability to provide reasoned technical pushback when reviewer suggestions conflict with architectural decisions or existing functionality.

Key Features

01YAGNI (You Ain't Gonna Need It) check for requested 'professional' features

021 GitHub stars

03Structured verification logic for unclear or ambiguous feedback

04Reasoned technical pushback patterns for incorrect suggestions

05Non-performative communication protocol to eliminate social fillers

06Context-aware skepticism for external versus internal review sources

Use Cases

01Processing complex, multi-point feedback from senior technical leads

02Filtering and verifying suggestions from external automated or human reviewers

03Clarifying ambiguous batch update requests before modifying the codebase

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add krosebrook/source-of-truth-monorepo receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill