What happens if a code review comment is unclear?

Claude is instructed to stop and request clarification on all ambiguous items before implementing any part of the feedback to avoid partial or incorrect fixes.

How does this skill help prevent over-engineering?

It includes a mandatory YAGNI check, prompting Claude to grep the codebase for actual usage before implementing suggested 'proper' features that might be unnecessary.

Why does Claude stop saying 'thank you' with this skill enabled?

To reduce communication noise and focus on action. The skill treats the implementation of the fix itself as the most effective form of acknowledgment.

How does this skill change Claude's personality?

It directs Claude to be more technically rigorous and less conversational, prioritizing factual accuracy and code quality over social pleasantries or performative agreement.

Technical Code Review Reception

Name: Technical Code Review Reception
Author: LyQing63

byLyQing63

0•

Collaboration Tools

Standardizes the reception of code review feedback by prioritizing technical verification and rigorous evaluation over performative agreement.

This skill transforms how Claude handles code review feedback by enforcing a strict protocol of technical verification before implementation. It discourages superficial agreement and 'gratitude' filler, instead focusing on restating requirements, checking codebase reality, and providing reasoned technical pushback when necessary. By integrating YAGNI (You Ain't Gonna Need It) principles and requiring full clarification for ambiguous tasks, it ensures that changes are technically sound, necessary, and correctly implemented without introducing regressions or over-engineered bloat.

Key Features

01Integrates YAGNI checks to prevent the implementation of unused or speculative features.

020 GitHub stars

03Enforces a verify-before-implement workflow to ensure technical correctness.

04Mandates total clarification of multi-item feedback before starting any code changes.

05Eliminates performative agreement and conversational filler for more efficient collaboration.

06Provides structured patterns for pushing back on technically unsound or unnecessary suggestions.

Use Cases

01Filtering out unnecessary 'professional' features that do not serve current project goals.

02Processing complex feedback from senior engineers or external reviewers with technical skepticism.

03Managing multi-item GitHub PR review threads with structured, sequential implementation.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lyqing63/lyqing.opencode receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill