OpenSkillIndex← back to search
claude-codedevelopment

Babysitter receiving-code-review

Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not blind implementation.

install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/superpowers/skills/receiving-code-review" ~/.claude/skills/a5c-ai-babysitter-receiving-code-review && rm -rf "$T"
manifest: library/methodologies/superpowers/skills/receiving-code-review/SKILL.md
tags
#code-review#verification#implementation#technical-evaluation
source content

Code Review Reception

Overview

Code review requires technical evaluation, not emotional performance. Verify before implementing. Ask before assuming.

Core principle: Verify before implementing.

Response Pattern

  1. READ - Complete feedback without reacting
  2. UNDERSTAND - Restate requirement in own words
  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

When to Push Back

  • Suggestion breaks existing functionality
  • Reviewer lacks full context
  • Violates YAGNI
  • Conflicts with architectural decisions

Tool Use

Referenced by implementation processes when handling review feedback.