AgentSkillsCN

receiving-code-review

在收到代码评审反馈后，尤其是在采纳建议之前，若反馈内容模糊不清或存在技术上的疑虑时，可优先选用此技能——这需要严谨的技术考量与充分的验证，而非表面化的认同或盲目的照搬。

SKILL.md
--- frontmatter
version: 4.1.0-fractal
name: receiving-code-review
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

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

code
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

code
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.

Example:

code
your human partner: "Fix 1-6"
You understand 1,2,3,6. Unclear on 4,5.

❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later
✅ RIGHT: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding."

Source-Specific Handling

🧠 Knowledge Modules (Fractal Skills)

1. From your human partner

2. From External Reviewers