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