code-review-reception

仓库创建 2026年3月12日最近提交 21 天前SkillHot 收录 20 天前

▸ 精选理由

适合需要技术严谨回复评审的个人或团队使用

这个 Skill 做什么

在接收代码评审时的回应流程，优先技术验证

收到代码评审意见时，先别急着点头或马上改，先技术性地验证对方建议是否正确。按照“完整读完—用自己话复述需求—验证假设”的流程去问清楚、复现或查证，避免表面同意却引入 bug。特别适用于对方意见含糊或看起来有技术问题的场景，强调事实和证据而不是社交礼貌。

▸ 展开 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. MANDATORY when catching yourself about to say 'Great suggestion!' or 'You're right!'.

Skill 开发管理代码评审交流规范验证优先通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/huanlongAI/tzh-Harness/main/cowork-skills/code-review-reception/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/huanlongAI/tzh-Harness/main/cowork-skills/code-review-reception/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 CLAUDE.md violation)
- "Great point!"

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