What is the core principle of the Receiving Code Review skill?

The core principle is to verify feedback before implementation. It prioritizes technical correctness and codebase reality over social comfort or 'performative' agreement.

How does this skill handle unclear feedback?

It enforces a full stop. If any item in a review is unclear, the skill dictates that you must ask for clarification on those specific items before implementing any part of the feedback.

Does it treat all reviewers the same?

No. It differentiates between 'trusted' human partners and external reviewers, applying a higher level of skepticism and cross-checking to feedback from external sources.

Why does this skill forbid saying 'Thank you' or 'Great point'?

To maintain technical focus. Expressions of gratitude are considered performative; the skill encourages stating technical facts or showing the fix in code instead of using social fillers.

When does this skill recommend pushing back on a reviewer?

Pushback is required if a suggestion breaks existing functionality, lacks context, violates YAGNI (unused features), or conflicts with established architectural decisions.

Code Review Reception

Name: Code Review Reception
Author: julianromli

byjulianromli

•

Collaboration Tools

Enforces technical rigor and objective verification when processing code review feedback to ensure architectural integrity.

The Code Review Reception skill shifts Claude's behavior from passive agreement to active technical evaluation when receiving feedback. It provides a structured framework for reading, understanding, and verifying suggestions against the actual codebase before any code is changed. By prioritizing technical correctness over social comfort, this skill prevents 'performative agreement,' filters out unnecessary 'YAGNI' features, and ensures that feedback—whether from a trusted partner or an external reviewer—is handled with the skepticism and validation required for high-quality software development.

Key Features

01Integrated YAGNI verification to prevent the implementation of unused or 'professional' bloat

02Structured 'Response Pattern' for systematic feedback evaluation

03Anti-performative communication filters that replace generic gratitude with technical action

04Protocol for graceful technical pushback and clarification of ambiguous requirements

0512 GitHub stars

06Context-aware handling for differentiating between core team and external reviewer feedback

Use Cases

01Ensuring architectural consistency when feedback conflicts with established project patterns

02Clarifying complex or multi-part feedback batches before starting implementation

03Validating external pull request suggestions against existing project constraints and legacy support

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add julianromli/opencode-template receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill