Why are 'Thank you' messages restricted?

To prioritize actions over words; the skill assumes that a correct technical implementation and a factual report of the fix are more valuable than social pleasantries.

What happens if a reviewer's suggestion is technically incorrect?

The skill prompts Claude to push back using technical reasoning and evidence from the codebase rather than blindly implementing the change.

How does it handle multiple feedback items at once?

It enforces a rule where Claude must clarify all items first, then implement them one-by-one with individual testing to prevent regressions.

How does this skill change Claude's personality?

It shifts Claude's tone from being overly polite or agreeable to being technically objective, removing performative phrases like 'You're absolutely right!' or 'Thanks!'

Does it work with external PR reviewers?

Yes, it includes specific handling for external feedback, applying extra skepticism to ensure suggestions fit the project's specific architectural context and legacy requirements.

Technical Code Review Protocol

Name: Technical Code Review Protocol
Author: claudiodearaujo

byclaudiodearaujo

0•

Collaboration Tools

Standardizes how Claude receives and implements code review feedback by prioritizing technical verification over performative agreement.

This skill implements a rigorous workflow for processing code reviews, ensuring that every suggestion is technically verified against the codebase before implementation. It eliminates performative social responses like 'Great point!' or 'Thanks!' in favor of factual, technical acknowledgment. By enforcing a 'verify before assuming' mindset, it prevents blind implementation of incorrect external suggestions, manages unclear feedback through proactive clarification, and adheres to YAGNI principles to keep the codebase lean and functional.

Key Features

01Elimination of performative or polite filler responses to maintain focus on accuracy

02Technical verification workflow to validate suggestions against codebase reality

03Proactive clarification protocol for ambiguous or multi-part review items

04Step-by-step implementation and testing strategy for complex feedback cycles

05Context-aware skepticism for external reviewer suggestions to prevent regressions

060 GitHub stars

Use Cases

01Responding to PR comments on GitHub or GitLab without social overhead

02Clarifying vague instructions from human partners before altering production code

03Evaluating complex refactoring suggestions from external contributors

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add claudiodearaujo/izacenter receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill