重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
verification-before-completion by secondsky/claude-skills
npx skills add https://github.com/secondsky/claude-skills --skill verification-before-completion未经验证即声称工作已完成是不诚实的行为,而非高效。
核心原则: 先有证据,再作声明,始终如此。
违反此规则的字面要求即违反其精神。
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
如果你尚未在当前消息中运行验证命令,则不能声称它已通过。
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 verifying
测试:
# 首选:bun
bun test
# 备选:npm
npm test
构建:
# 首选:bun
bun run build
# 备选:npm
npm run build
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
代码检查:
# 首选:bun
bun run lint
# 备选:npm
npm run lint
类型检查:
# 首选:bun
bunx tsc --noEmit
# 或:npx tsc --noEmit
| 声明 | 要求 | 不足够 |
|---|---|---|
| 测试通过 | 测试命令输出:0 个失败 | 之前的运行结果,"应该通过" |
| 代码检查干净 | 代码检查输出:0 个错误 | 部分检查,推测 |
| 构建成功 | 构建命令:退出码 0 | 代码检查通过,日志看起来没问题 |
| Bug 已修复 | 测试原始症状:通过 | 代码已更改,假设已修复 |
| 回归测试有效 | 红绿循环已验证 | 测试通过一次 |
| 代理已完成 | VCS 差异显示更改 | 代理报告"成功" |
| 需求已满足 | 逐行核对清单 | 测试通过 |
| 借口 | 现实 |
|---|---|
| "现在应该能工作了" | 运行验证 |
| "我有信心" | 信心 ≠ 证据 |
| "就这一次" | 没有例外 |
| "代码检查通过了" | 代码检查 ≠ 编译器 |
| "代理说成功了" | 独立验证 |
| "我累了" | 疲惫 ≠ 借口 |
| "部分检查就够了" | 部分证明不了什么 |
| "措辞不同所以规则不适用" | 精神重于字面 |
测试:
✅ [运行测试命令] [查看:34/34 通过] "所有测试通过"
❌ "现在应该能通过" / "看起来正确"
回归测试(TDD 红绿循环):
✅ 编写 → 运行(通过)→ 还原修复 → 运行(必须失败)→ 恢复 → 运行(通过)
❌ "我写了一个回归测试"(未经红绿验证)
构建:
✅ [运行构建] [查看:退出码 0] "构建通过"
❌ "代码检查通过了"(代码检查不检查编译)
需求:
✅ 重读计划 → 创建核对清单 → 验证每一项 → 报告差距或完成情况
❌ "测试通过,阶段完成"
代理委托:
✅ 代理报告成功 → 检查 VCS 差异 → 验证更改 → 报告实际状态
❌ 相信代理报告
来自失败的记忆:
总是在以下情况之前:
规则适用于:
验证没有捷径。
运行命令。阅读输出。然后声明结果。
这是不容商量的。
每周安装
69
仓库
GitHub 星标
91
首次出现
Jan 25, 2026
安全审计
安装于
claude-code62
gemini-cli55
codex55
opencode55
cursor55
github-copilot51
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.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes.
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 verifying
Tests:
# Preferred: bun
bun test
# Alternative: npm
npm test
Build:
# Preferred: bun
bun run build
# Alternative: npm
npm run build
Lint:
# Preferred: bun
bun run lint
# Alternative: npm
npm run lint
Type check:
# Preferred: bun
bunx tsc --noEmit
# or: npx tsc --noEmit
| 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 |
| 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 |
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
From failure memories:
ALWAYS before:
Rule applies to:
No shortcuts for verification.
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
Weekly Installs
69
Repository
GitHub Stars
91
First Seen
Jan 25, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
claude-code62
gemini-cli55
codex55
opencode55
cursor55
github-copilot51
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
122,000 周安装