Does this skill work for GitHub PR comments?

Yes, it specifically includes instructions to reply within the relevant GitHub comment thread rather than posting top-level comments, maintaining a clean review history.

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

This skill prioritizes actions over words. By removing performative agreement, Claude focuses on technical verification and implementation, ensuring that the code itself demonstrates that the feedback was understood.

When will Claude push back on a reviewer's suggestion?

Claude will push back using technical reasoning if a suggestion breaks existing functionality, violates YAGNI principles, is technically incorrect for the specific stack, or lacks necessary context.

How does this skill handle unclear feedback?

It enforces a 'STOP' protocol. If any part of the feedback is unclear, the skill requires asking for clarification before implementing any changes to prevent partial or incorrect fixes.

Technical Code Review Reception

Name: Technical Code Review Reception
Author: tianzecn

bytianzecn

•

Collaboration Tools

Enforces technical rigor and verification when processing code review feedback to prioritize correctness over social agreement.

The Technical Code Review Reception skill optimizes how Claude interacts with human and external code reviews by enforcing a 'verify-before-implementing' workflow. It provides a structured framework for evaluating feedback against the existing codebase, handling ambiguous requests, and pushing back on technically questionable or redundant suggestions (YAGNI). By eliminating performative language and focus-stealing gratitude, it ensures that all modifications are driven by technical necessity and codebase reality rather than blind adherence to comments.

Key Features

01Prohibition of performative agreement and gratitude-based filler language.

02Categorized handling for trusted human partners versus external reviewers.

03Structured 'Read-Understand-Verify' response pattern for all feedback.

04Integrated YAGNI verification to prevent over-engineering during reviews.

05Formalized technical pushback protocols based on codebase evidence.

061 GitHub stars

Use Cases

01Navigating complex pull request reviews where suggestions may conflict with architecture.

02Clarifying ambiguous or batch feedback before beginning implementation to avoid regressions.

03Ensuring external reviewer suggestions are technically sound for the specific project stack.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add tianzecn/myclaudecode receiving-code-review

For use in Claude.ai and ChatGPT

Download Skill