How does it handle unclear instructions?

It stops implementation entirely until all points are clarified to prevent partial or incorrect changes that might conflict with other feedback items.

What is the 'YAGNI check' in this context?

Before implementing 'proper' features suggested by reviewers, it greps the codebase to see if the feature is actually used, suggesting removal if it is unnecessary.

Why does this skill prohibit saying 'Thank you'?

It prioritizes technical action over social performance; the fix itself serves as the acknowledgment, keeping communication concise and technical.

Does it follow all suggestions automatically?

No, it encourages technical skepticism and pushback if a suggestion breaks compatibility, lacks context, or violates YAGNI principles.

Technical Code Review Reception

Name: Technical Code Review Reception
Author: franroa

byfranroa

协作工具

Processes code review feedback with technical rigor and verification instead of performative agreement.

关于

This skill ensures Claude approaches code reviews as a technical evaluator rather than a social assistant. It establishes a strict protocol for verifying suggestions against the codebase, pushing back on technically unsound advice, and prioritizing clarity before implementation. By eliminating 'politeness bloat' and focusing on technical correctness, it helps maintain architectural integrity and prevents the introduction of unnecessary features or breaking changes through a 'verify-before-implement' workflow.

主要功能

0 GitHub stars
Technical verification protocol for all review suggestions
YAGNI-driven evaluation of suggested features
Requirement-first clarification for ambiguous feedback
Elimination of performative agreement and polite filler text
Structured implementation order for multi-item reviews

使用场景

Managing complex refactoring requests with multiple dependencies
Evaluating suggestions from external automated reviewers or third-party audits
Handling critical feedback from human senior developers

关于

主要功能

0 GitHub stars
Technical verification protocol for all review suggestions
YAGNI-driven evaluation of suggested features
Requirement-first clarification for ambiguous feedback
Elimination of performative agreement and polite filler text
Structured implementation order for multi-item reviews

使用场景

Managing complex refactoring requests with multiple dependencies
Evaluating suggestions from external automated reviewers or third-party audits
Handling critical feedback from human senior developers