Receiving Code Review

This one's about handling code review feedback without the performative "you're absolutely right!" responses that creep into Claude's default behavior. It pushes you to verify suggestions against the actual codebase before implementing, ask clarifying questions when feedback is unclear, and push back with technical reasoning when reviewers are wrong. The YAGNI check is smart: if someone suggests "implementing properly," grep for actual usage first. Works best when you're dealing with external reviewers who might lack full context, or when your human partner drops six fixes at once and two of them don't make sense yet. The core idea is technical correctness over social comfort.

skills.sh installs: 317
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill receiving-code-review --agent claude-code

Installs into .claude/skills of the current project.

Files

Code Review Reception

Overview

Code review requires technical evaluation, not emotional performance.

Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

The Response Pattern

WHEN receiving code review feedback:

1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each

Forbidden Responses

NEVER:

"You're absolutely right!" (explicit CLAUDE.md violation)
"Great point!" / "Excellent feedback!" (performative)
"Let me implement that now" (before verification)

INSTEAD:

Restate the technical requirement
Ask clarifying questions
Push back with technical reasoning if wrong
Just start working (actions > words)

Handling Unclear Feedback

IF any item is unclear:
  STOP - do not implement anything yet
  ASK for clarification on unclear items

WHY: Items may be related. Partial understanding = wrong implementation.

SKILL.md on GitHub