What happens if code review feedback is unclear?

The skill mandates a full stop on all implementations until every item is clarified, preventing partial or potentially conflicting code changes.

Why does this skill discourage saying 'Thank you'?

It prioritizes technical action over social performance. The fix itself serves as the acknowledgment of correct feedback, keeping the focus on code quality.

How does it handle feedback from external reviewers?

It treats external feedback with healthy skepticism, requiring Claude to verify suggestions against the specific codebase reality and existing functionality before proceeding.

What is the benefit of the YAGNI check feature?

It prevents 'over-engineering' by checking if a suggested feature or refactor is actually necessary based on the current usage within the codebase.

How does Claude push back on incorrect suggestions?

Claude uses factual technical reasoning, references existing tests, and highlights potential regressions instead of being defensive or agreeable.

Technical Code Review Handler

Name: Technical Code Review Handler
Author: yusoofsh

byyusoofsh

0•

Collaboration Tools

Evaluates code review feedback with technical rigor, ensuring verification and clarity before implementation while avoiding performative agreement.

This skill equips Claude with a structured framework for processing code review feedback by prioritizing technical accuracy over social etiquette. It enforces a strict protocol of reading, understanding, verifying, and evaluating suggestions against the existing codebase before any changes are made. By discouraging performative responses like 'Great point!' or 'You're absolutely right!', it focuses the interaction on technical correctness, identifies unnecessary features through YAGNI checks, and ensures that unclear feedback is clarified before partial or incorrect implementations occur.

Key Features

01Strict verification protocol to prevent blind implementation of suggestions

02Automated YAGNI checks to prevent the addition of unused or speculative features

03Context-aware skepticism for external reviewers vs. trusted human partners

04Elimination of performative conversational fillers and redundant gratitude

05Structured clarification process for handling ambiguous or multi-part feedback

060 GitHub stars

Use Cases

01Evaluating external contributions against local project architectural constraints

02Processing complex feedback lists from lead developers without missing nuances

03Pushing back on technically incorrect or legacy-breaking review suggestions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add yusoofsh/dotfiles receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill