verify
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseVerification Before Completion
完成前的验证
Overview
概述
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
宣称工作已完成却未进行验证是不诚信的行为，绝非高效之举。
核心原则： 始终坚持‘先有证据，后下断言’。
违反规则的字面要求即违反规则的精神内核。
The Iron Law
铁律
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCEIf you haven't run the verification command in this message, you cannot claim it passes.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE如果未运行本规则中提及的验证命令，你不得宣称工作已通过。
The Gate Function
把关流程
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifyingBEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
Skip any step = lying, not verifyingCommon Failures
常见失误
| Claim | Requires | Not Sufficient |
|---|---|---|
| Tests pass | Test command output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build command: exit 0 | Linter passing, logs look good |
| Bug fixed | Test original symptom: passes | Code changed, assumed fixed |
| Regression test works | Red-green cycle verified | Test passes once |
| Agent completed | VCS diff shows changes | Agent reports "success" |
| Requirements met | Line-by-line checklist | Tests passing |
| 宣称 | 所需验证 | 不足以证明的情况 |
|---|---|---|
| 测试通过 | 测试命令输出：0失败 | 之前的运行结果、“应该能通过” |
| 代码检查器无问题 | 代码检查器输出：0错误 | 部分检查、推断 |
| 构建成功 | 构建命令：退出码0 | 代码检查器通过、日志看起来正常 |
| 漏洞已修复 | 测试原始症状：通过 | 代码已修改、假设已修复 |
| 回归测试有效 | 已验证红绿循环 | 测试仅通过一次 |
| Agent已完成任务 | VCS差异显示有变更 | Agent报告“成功” |
| 需求已满足 | 逐条核对检查清单 | 测试通过 |
Red Flags - STOP
危险信号——立即停止
- Using "should", "probably", "seems to"
- Expressing satisfaction before verification ("Great!", "Perfect!", "Done!", etc.)
- About to commit/push/PR without verification
- Trusting agent success reports
- Relying on partial verification
- Thinking "just this once"
- Tired and wanting work over
- ANY wording implying success without having run verification
- 使用“应该”“大概”“似乎”等词汇
- 未验证就表达满意（如“太棒了！”“完美！”“完成了！”等）
- 未验证就准备提交/推送/创建PR
- 信任Agent的成功报告
- 依赖部分验证
- 抱有“就这一次”的想法
- 因疲惫想结束工作
- 任何未运行验证就暗示成功的表述
Rationalization Prevention
避免合理化借口
| Excuse | Reality |
|---|---|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ compiler |
| "Agent said success" | Verify independently |
| "I'm tired" | Exhaustion ≠ excuse |
| "Partial check is enough" | Partial proves nothing |
| "Different words so rule doesn't apply" | Spirit over letter |
| 借口 | 事实 |
|---|---|
| “现在应该能正常运行了” | 运行验证命令 |
| “我很有信心” | 信心≠证据 |
| “就这一次” | 没有例外 |
| “代码检查器通过了” | 代码检查器≠编译器 |
| “Agent说成功了” | 独立验证 |
| “我累了” | 疲惫≠借口 |
| “部分检查就足够了” | 部分检查无法证明任何事 |
| “换个说法规则就不适用了” | 精神重于字面 |
Key Patterns
关键模式
Tests:
✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"Regression tests (TDD Red-Green):
✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)Build:
✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)Requirements:
✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"Agent delegation:
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report测试：
✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"回归测试（TDD红绿循环）：
✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)构建：
✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)需求：
✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"Agent委托：
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent reportWhy This Matters
为什么这很重要
From 24 failure memories:
- your human partner said "I don't believe you" - trust broken
- Undefined functions shipped - would crash
- Missing requirements shipped - incomplete features
- Time wasted on false completion → redirect → rework
- Violates: "Honesty is a core value. If you lie, you'll be replaced."
基于24次失败案例：
- 你的人类搭档说“我不信你”——信任破裂
- 未定义的函数被发布——会导致崩溃
- 遗漏的需求被发布——功能不完整
- 因虚假完成浪费时间→重新调整→返工
- 违反：“诚信是核心价值观。若你撒谎，将被替换。”
When To Apply
适用场景
ALWAYS before:
- ANY variation of success/completion claims
- ANY expression of satisfaction
- ANY positive statement about work state
- Committing, PR creation, task completion
- Moving to next task
- Delegating to agents
Rule applies to:
- Exact phrases
- Paraphrases and synonyms
- Implications of success
- ANY communication suggesting completion/correctness
始终在以下操作前应用：
- 任何形式的成功/完成宣称
- 任何表达满意的表述
- 任何关于工作状态的正面陈述
- 提交代码、创建PR、标记任务完成
- 进入下一个任务
- 委托任务给Agent
规则适用于：
- 精确表述
- 改写和同义词
- 暗示成功的表述
- 任何表明完成/正确性的沟通
The Bottom Line
底线
No shortcuts for verification.
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
验证没有捷径。
运行命令。查看输出。然后再宣称结果。
这是不容协商的。