Skip to content
Skill

receiving-code-review

by obra

AI Summary

Helps developers critically evaluate code review feedback by verifying technical soundness before implementation, preventing blind acceptance of potentially incorrect suggestions.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "receiving-code-review" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/receiving-code-review && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/receiving-code-review/SKILL.md "https://raw.githubusercontent.com/obra/superpowers/main/skills/receiving-code-review/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Overview

Code review requires technical evaluation, not emotional performance. Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

YAGNI Check for "Professional" Features

` IF reviewer suggests "implementing properly": grep codebase for actual usage IF unused: "This endpoint isn't called. Remove it (YAGNI)?" IF used: Then implement properly ` your human partner's rule: "You and reviewer both report to me. If we don't need this feature, don't add it."

Real Examples

Performative Agreement (Bad): ` Reviewer: "Remove legacy code" ❌ "You're absolutely right! Let me remove that..." ` Technical Verification (Good): ` Reviewer: "Remove legacy code" ✅ "Checking... build target is 10.15+, this API needs 13+. Need legacy for backward compat. Current impl has wrong bundle ID - fix it or drop pre-13 support?" ` YAGNI (Good): ` Reviewer: "Implement proper metrics tracking with database, date filters, CSV export" ✅ "Grepped codebase - nothing calls this endpoint. Remove it (YAGNI)? Or is there usage I'm missing?" ` Unclear Item (Good): ` your human partner: "Fix items 1-6" You understand 1,2,3,6. Unclear on 4,5. ✅ "Understand 1,2,3,6. Need clarification on 4 and 5 before implementing." `

The Response Pattern

` WHEN receiving code review feedback: • READ: Complete feedback without reacting • UNDERSTAND: Restate requirement in own words (or ask) • VERIFY: Check against codebase reality • EVALUATE: Technically sound for THIS codebase? • RESPOND: Technical acknowledgment or reasoned pushback • IMPLEMENT: One item at a time, test each `

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 13d ago
Active
Adoption1K+ stars on GitHub
162.8k ★ · Popular
DocsREADME + description
Well-documented

GitHub Signals

Stars162.8k
Forks14.2k
Issues306
Updated13d ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code