Why does this skill ban saying 'thank you' or 'great point'?

To ensure the AI focuses on technical correctness rather than performative social cues. In this workflow, actions and code fixes are considered the only necessary acknowledgment of valid feedback.

How does it differentiate between a human partner and external reviewers?

It treats human partners as trusted sources while still requiring technical understanding, whereas it applies a higher level of skepticism and rigorous cross-platform verification to external reviewer suggestions.

What is the 'YAGNI' check mentioned in the skill?

Claude is directed to grep the codebase to see if a suggested feature or 'proper' implementation is actually needed by the current system, pushing back if the suggestion adds unnecessary complexity.

How does this skill handle unclear feedback?

It instructs Claude to stop and ask for clarification on all items before implementing any part of the feedback, preventing partial or incorrect changes that might result from assuming intent.

Code Review Technical Rigor

Name: Code Review Technical Rigor
Author: seanGSISG

byseanGSISG

コラボレーションツール

Enforces a technical, non-performative approach to processing and implementing code review feedback with strict verification.

概要

This skill transforms how Claude handles code reviews by prioritizing technical verification over social compliance. It guides Claude to avoid performative language like 'Great point!' and instead focuses on restating requirements, verifying suggestions against the actual codebase, and pushing back when suggestions violate YAGNI principles or architectural decisions. It is particularly useful for ensuring that feedback is critically evaluated before implementation to prevent regressions, unnecessary feature bloat, or blind adherence to incorrect suggestions.

主な機能

Eliminates performative agreement and 'gratitude spam' in favor of technical action.
Implements a structured response pattern: Read, Understand, Verify, Evaluate, Respond, and Implement.
Enforces a mandatory verification step against the current codebase before applying any changes.
Handles unclear or multi-item feedback by requiring clarification before any implementation begins.
Provides specific protocols for evaluating external reviewer suggestions versus trusted partner feedback.
0 GitHub stars

ユースケース

Protecting a codebase from 'feature creep' or unnecessary 'best practice' suggestions that do not apply to the specific stack.
Processing complex feedback from multiple external reviewers with varying levels of context.
Managing large, multi-point code reviews where items may be technically interrelated or conflicting.

概要

主な機能

Eliminates performative agreement and 'gratitude spam' in favor of technical action.
Implements a structured response pattern: Read, Understand, Verify, Evaluate, Respond, and Implement.
Enforces a mandatory verification step against the current codebase before applying any changes.
Handles unclear or multi-item feedback by requiring clarification before any implementation begins.
Provides specific protocols for evaluating external reviewer suggestions versus trusted partner feedback.
0 GitHub stars

ユースケース

Protecting a codebase from 'feature creep' or unnecessary 'best practice' suggestions that do not apply to the specific stack.
Processing complex feedback from multiple external reviewers with varying levels of context.
Managing large, multi-point code reviews where items may be technically interrelated or conflicting.