What is the core principle of this code review skill?

The core principle is to verify before implementing. It treats external feedback as suggestions to be evaluated against the codebase reality rather than orders to be followed blindly.

Why does this skill discourage saying 'Thanks' or 'Great point'?

The skill prioritizes technical rigor over emotional performance. By avoiding performative gratitude, Claude focuses on verified implementation and technical correctness rather than social pleasantries.

How does the skill handle unclear feedback?

It instructs Claude to stop and ask for clarification on all items before implementing any. This prevents the risk of partial understanding leading to incorrect or conflicting implementations.

Can Claude push back on reviewer suggestions with this skill?

Yes. The skill provides a framework for professional, technical pushback when suggestions break functionality, lack context, violate YAGNI principles, or conflict with prior architectural decisions.

Technical Code Review Reception

Name: Technical Code Review Reception
Author: claudiodearaujo

byclaudiodearaujo

0•

Collaboration Tools

Standardizes how code review feedback is evaluated and implemented with a focus on technical rigor over performative agreement.

This skill equips Claude with a structured framework for handling code review feedback, ensuring technical accuracy and alignment with the existing codebase. It moves beyond simple performative agreement by requiring Claude to verify suggestions, ask clarifying questions, and push back against technically unsound or unnecessary (YAGNI) changes. By following a rigorous response pattern, it prevents blind implementations and ensures that every change is intentional, tested, and contextually appropriate for the specific project environment.

Key Features

01Elimination of performative or emotional responses to maintain technical focus

02Strategic handling of unclear feedback to prevent partial implementations

03Contextual evaluation against YAGNI principles to avoid over-engineering

04Guidelines for technical pushback based on codebase reality and project context

05Structured six-step verification process for all feedback items

060 GitHub stars

Use Cases

01Managing multi-item feedback lists by prioritizing blocking issues and testing individually

02Evaluating and filtering suggestions from external automated review tools

03Processing complex pull request feedback from human collaborators

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/sistema-de-narra-o-de-livro-front receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill

Key Features

01Elimination of performative or emotional responses to maintain technical focus

02Strategic handling of unclear feedback to prevent partial implementations

03Contextual evaluation against YAGNI principles to avoid over-engineering

04Guidelines for technical pushback based on codebase reality and project context

05Structured six-step verification process for all feedback items

060 GitHub stars

Use Cases

01Managing multi-item feedback lists by prioritizing blocking issues and testing individually

02Evaluating and filtering suggestions from external automated review tools

03Processing complex pull request feedback from human collaborators

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/sistema-de-narra-o-de-livro-front receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill