Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not blind implementation.
Scanned 5/29/2026
Install to Claude Code
Skills Directorynpx -y skills add a5c-ai/babysitter --skill receiving-code-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Receiving Code Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-receiving-code-review)More formats (shields.io, HTML) on the badges page.
---
name: receiving-code-review
description: Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not blind implementation.
---
# 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
