How does the skill help with pushing back on suggestions?

It provides a framework for using technical reasoning and factual data, such as database constraints or performance benchmarks, to explain why a suggestion might be harmful.

What is the YAGNI check in this context?

It is a check to see if a suggested feature is actually used in the current codebase before implementing it, helping to prevent unnecessary technical debt.

Can I use this for both human and automated reviews?

Yes, it provides specific handling logic for human partners and external reviewers to ensure technical context is always respected regardless of the source.

Why does this skill ban phrases like 'thank you' or 'you're right'?

To prevent performative agreement and ensure that every code change is based on objective technical verification rather than social compliance.

How does the skill handle unclear feedback?

It mandates stopping implementation and asking for clarification before any work begins, preventing partial understanding from leading to incorrect fixes.

Code Review Reception

Name: Code Review Reception
Author: samjhecht

bysamjhecht

•

Herramientas de Colaboración

Standardizes technical evaluation of code review feedback by prioritizing verification and technical rigor over performative agreement.

Acerca de

The Code Review Reception skill provides a structured framework for AI agents to process feedback with technical integrity. It enforces a protocol of verifying suggestions against the actual codebase, performing cost-benefit analyses, and applying YAGNI principles before implementation. By eliminating performative language and emphasizing technical reasoning, this skill ensures that code changes are driven by correctness and maintainability rather than social compliance, making it essential for high-stakes development environments.

Características Principales

Rigorous technical verification protocol to prevent blind implementation
Step-by-step implementation workflow with individual testing for each fix
Strict prohibition of performative agreement and unproductive social language
Structured response patterns for both human partners and external reviewers
1 GitHub stars
Automatic YAGNI (You Ain't Gonna Need It) usage verification for new features

Casos de Uso

Clarifying ambiguous multi-step feedback from team leads before writing code
Evaluating complex architectural suggestions from external reviewers for technical feasibility
Pushing back on technically incorrect or unnecessary feature requests with data-backed reasoning

Acerca de

Características Principales

Rigorous technical verification protocol to prevent blind implementation
Step-by-step implementation workflow with individual testing for each fix
Strict prohibition of performative agreement and unproductive social language
Structured response patterns for both human partners and external reviewers
1 GitHub stars
Automatic YAGNI (You Ain't Gonna Need It) usage verification for new features

Casos de Uso

Clarifying ambiguous multi-step feedback from team leads before writing code
Evaluating complex architectural suggestions from external reviewers for technical feasibility
Pushing back on technically incorrect or unnecessary feature requests with data-backed reasoning