How does this skill handle unclear feedback?

It instructs the AI to halt implementation immediately and ask for clarification, preventing the risk of partial or incorrect code changes based on assumptions.

What happens if a reviewer suggests a feature that isn't needed?

The skill triggers a YAGNI (You Ain't Gonna Need It) check, grepping the codebase for usage and pushing back if the suggestion adds unnecessary complexity.

Why does the skill discourage saying 'Thank you'?

To maintain a focus on technical rigor. In professional code reviews, the best acknowledgment of feedback is a correct, verified implementation rather than verbal gratitude.

What is performative agreement in code reviews?

Performative agreement refers to social filler like 'You're absolutely right!' or 'Great catch!' that focuses on social comfort rather than technical validation of the suggested change.

Can I use this for both internal and external reviews?

Yes, the skill includes specific logic to treat human partner feedback with trust while applying higher skepticism and context-checking to external reviewers.

Code Review Integrity

Name: Code Review Integrity
Author: julianromli

byjulianromli

•

101

•

Collaboration Tools

Ensures technical rigor when processing code review feedback by prioritizing verification over performative agreement.

This skill optimizes how Claude processes and responds to code review feedback, replacing polite but empty agreement with a systematic, technical evaluation protocol. It enforces a 'Verify before Implementing' workflow that requires the AI to restate requirements, check codebase reality, and provide reasoned pushback when suggestions are technically questionable or violate YAGNI principles. By eliminating conversational filler and performative gratitude, the skill maintains a high bar for architectural consistency and ensures that every change is intentional, tested, and aligned with the project's specific constraints.

Key Features

01Enforces a structured Read-Understand-Verify-Evaluate-Respond pattern

02101 GitHub stars

03Standardizes professional pushback protocols for incorrect or conflicting feedback

04Provides specific logic for handling trusted partners versus external reviewers

05Automates YAGNI checks to prevent the implementation of unnecessary features

06Eliminates performative agreement and non-technical conversational filler

Use Cases

01Ensuring new implementations don't introduce regressions or over-engineered features

02Processing high-volume PR feedback where technical accuracy is more important than social niceties

03Maintaining codebase stability when receiving suggestions from reviewers who lack full project context

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