receiving-code-review

仓库创建 2026年6月29日最近提交 22 天前SkillHot 收录 22 天前

▸ 精选理由

强调技术核实与沟通，适合希望改进review流程的开发者。

这个 Skill 做什么

在接收代码评审反馈时提供核验流程与澄清建议，避免盲从或误解。

收到代码评审意见别急着改，先按流程核验和澄清：完整读反馈、用自己的话复述需求、验证技术可行性再实施，避免盲从或表演式同意。适用于对含糊或可疑建议做回应时，强调技术严谨优于社交安抚。这样能减少误改、返工和因误解导致的问题。

▸ 展开 SKILL.md 英文原文

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

开发编程代码审查反馈处理技术核验通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/receiving-code-review/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/MaximoCorrea1/ultra-powers/main/flows/ultra-powers/skills/receiving-code-review/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# 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

```
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 instruction-file violation)
- "Great

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有