Home / jnmetacode / superpowers-zh · GitHub

verification-before-completion SKILL.md skillA

verification-before-completion 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/verification-before-completion@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/verification-before-completion/SKILL.md
Versions recorded: 3
Latest version: v1.0.0, committed Aug 7, 2026
First version recorded: Mar 20, 2026
Size: 3,624 bytes
Repository stars: 8,348
License: MIT

在宣称工作完成、已修复或测试通过之前使用，在提交或创建 PR 之前——必须运行验证命令并确认输出后才能声称成功；始终用证据支撑断言.

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. 只有这时：才能做出结论

跳过任何一步 = 说谎，不是验证
```

## 常见失败模式

| 结论 | 需要 | 不够格 |
|------|------|--------|
| 测试通过 | 测试命令输出：0 failures | 之前的运行结果、"应该会通过" |
| Linter 无报错 | Linter 输出：0 errors | 部分检查、推断 |
| 构建成功 | 构建命令：exit 0 | linter 通过、日志看起来没问题 |
| Bug 已修复 | 测试原始症状：通过 | 代码改了，假设已修复 |
| 回归测试有效 | 红-绿循环已验证 | 测试只通过了一次 |
| 代理已完成 | VCS diff 显示变更 | 代理报告"成功" |
| 需求已满足 | 逐项核对清单 | 测试通过 |

## 红线——停下来

- 使用"应该"、"大概"、"似乎"
- 验证前就表达满意（"太好了！"、"完美！"、"搞定！"等）
- 即将提交/推送/创建 PR 却没有验证
- 信任代理的成功报告
- 依赖部分验证
- 想着"就这一次"
- 累了想赶紧收工
- **任何暗示成功但实际未运行验证的措辞**

## 防止合理化

| 借口 | 现实 |
|------|------|
| "应该能行了" | 运行验证命令 |
| "我有信心" | 信心 ≠ 证据 |
| "就这一次" | 没有例外 |
| "Linter 通过了" | Linter ≠ 编译器 |
| "代理说成功了" | 独立验证 |
| "我累了" | 疲劳 ≠ 借口 |
| "部分检查就够了" | 部分检查什么也证明不了 |
| "换个说法这条规则就不适用了" | 精神大于字面 |

## 关键模式

**测试：**
```
✅ [运行测试命令] [看到：34/34 pass] "全部测试通过"
❌ "应该能通过了" / "看起来对了"
```

**回归测试（TDD 红-绿）：**
```
✅ 编写 → 运行（通过）→ 回退修复 → 运行（必须失败）→ 恢复 → 运行（通过）
❌ "我写了回归测试"（没有经过红-绿验证）
```
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add jnmetacode/superpowers-zh/verification-before-completion@sha256:bd976c5f28413d08

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_2nt4eveurk3fkua4.svg)](https://markdownregistry.com/a/art_2nt4eveurk3fkua4)

5 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	3,624 B	A	view · diff
v1.0.0	2026-06-16	952fc29	4,163 B	A	view · diff
git:20260320.80bc100	2026-03-20	80bc100	4,079 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 (3624 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_2nt4eveurk3fkua4
GET https://markdownregistry.com/api/v1/resolve?ref=jnmetacode/superpowers-zh/verification-before-completion
GET https://markdownregistry.com/api/v1/blob/bd976c5f28413d08b3a7dc3026549a6ff43fab4e282b74842a9389cc2034eda4

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 · 在任何创造性工作之前必须使用此技能——创建功能、构建组件、添加功能、修改行为，或筹划任何新东西，无论是软件还是软件之外（一场分享、一门生意、一次装修）。