Home / jnmetacode / superpowers-zh · GitHub

receiving-code-review SKILL.md skillA

receiving-code-review from jnmetacode/superpowers-zh is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add jnmetacode/superpowers-zh/receiving-code-review@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: jnmetacode/superpowers-zh
Path: skills/receiving-code-review/SKILL.md
Versions recorded: 3
Latest version: v1.0.0, committed Aug 7, 2026
First version recorded: Mar 20, 2026
Size: 6,216 bytes
Repository stars: 8,348
License: MIT

收到代码审查反馈后、实施建议之前使用，尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证，而非敷衍附和或盲目执行.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 接收代码审查

## 概述

代码审查需要的是技术评估，不是情绪表演。

**核心原则：** 先验证再实施。先提问再假设。技术正确性优先于社交舒适度。

## 响应模式

```
收到代码审查反馈时：

1. 阅读：完整阅读反馈，不急于反应
2. 理解：用自己的话复述需求（或提问）
3. 验证：对照代码库的实际情况检查
4. 评估：对这个代码库来说技术上合理吗？
5. 回应：技术性确认或有理有据的反驳
6. 实施：一次一项，逐个测试
```

## 禁止的回应

**绝不要说：**
- "你说得太对了！"（明确违反 CLAUDE.md 规定）
- "好观点！"/"反馈很棒！"（敷衍表演）
- "让我立刻实施"（在验证之前）

**应该这样做：**
- 复述技术需求
- 提出澄清性问题
- 如果审查意见有误，用技术理由反驳
- 直接动手做（行动胜于言辞）

## 处理不明确的反馈

```
如果有任何一项不明确：
  停下来——先不要实施任何内容
  就不明确的项目提出澄清

为什么：各项之间可能有关联。部分理解 = 错误实施。
```

**示例：**
```
搭档："修复第 1-6 项"
你理解 1、2、3、6。对 4、5 不确定。

❌ 错误做法：先实施 1、2、3、6，稍后再问 4、5
✅ 正确做法："第 1、2、3、6 项我理解了。第 4 和第 5 项需要澄清后再动手。"
```

## 按来源区别处理

### 来自搭档的反馈
- **可信赖** —— 理解后直接实施
- **仍然要问** 如果范围不明确
- **不要敷衍附和**
- **直接行动** 或给出技术性确认

### 来自外部审查者的反馈
```
实施之前：
  1. 检查：对这个代码库来说技术上正确吗？
  2. 检查：是否会破坏现有功能？
  3. 检查：当前实现这样写是否有原因？
  4. 检查：在所有平台/版本上都适用吗？
  5. 检查：审查者了解完整上下文吗？

如果建议似乎有误：
  用技术理由反驳

如果无法轻易验证：
  说明情况："没有 [X] 我无法验证这一点。我应该 [调查/提问/先做]？"

如果与搭档之前的决策冲突：
  先停下来和搭档讨论
```

**搭档的原则：** "对外部反馈要持怀疑态度，但要仔细核实"

## YAGNI 检查——针对"专业化"功能建议

```
如果审查者建议"正规地实现"：
  在代码库中 grep 实际使用情况

  如果没人用："这个接口没有被调用。删掉它（YAGNI）？"
  如果有人用：那就正规实现
```

**搭档的原则：** "你和审查者都对我负责。如果我们不需要这个功能，就不要加。"

## 实施顺序

```
对于包含多项的反馈：
  1. 先澄清所有不明确的项
  2. 然后按以下顺序实施：
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add jnmetacode/superpowers-zh/receiving-code-review@sha256:f8d534ce6edf899a

The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_lc7xvnoewtkx266w.svg)](https://markdownregistry.com/a/art_lc7xvnoewtkx266w)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Mar 20, 2026 and Aug 7, 2026, about one every 70 days.

version	committed	commit	size	audit
v1.0.0 latest	2026-08-07	02d2551	6,216 B	A	view · diff
v1.0.0	2026-06-16	952fc29	6,383 B	A	view · diff
git:20260320.80bc100	2026-03-20	80bc100	6,309 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6216 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

jnmetacode/superpowers-zh · 8,348 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lc7xvnoewtkx266w
GET https://markdownregistry.com/api/v1/resolve?ref=jnmetacode/superpowers-zh/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/f8d534ce6edf899aafbb6054a86e8f1da0187c118be0b4039d86cfde611c5a34

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from jnmetacode/superpowers-zh

AGENTS.md AGENTS.md file

jnmetacode/superpowers-zh · AGENTS.md

git:20260510.a9e02b5 · audit B · 8,348 stars

CLAUDE.md CLAUDE.md file

jnmetacode/superpowers-zh · CLAUDE.md

git:20260907.3437ce2 · audit A · 8,348 stars

brainstorming SKILL.md skill

jnmetacode/superpowers-zh · skills/brainstorming/SKILL.md · 在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能、修改行为，或筹划任何新东西，无论是软件还是软件之外（一场分享、一门生意、一次装修）。