$ loading_
在宣布任务完成前运行验证命令并核对结果，确保结论可靠无误。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "Verification Before Completion" 技能： 1. 下载 https://raw.githubusercontent.com/obra/clank/main/skills/debugging/verification-before-completion/SKILL.md 2. 保存为 ~/.claude/skills/verification-before-completion/SKILL.md 3. 装好后重载技能，告诉我可以用了
我刚修改了登录模块，请在说明任务完成前先运行相关测试命令，检查是否全部通过，并贴出关键输出结果与失败项说明。
返回测试执行结果、通过/失败状态，以及基于输出得出的完成结论。
在确认可以部署前，请先执行构建和本地启动验证命令，确认没有报错，并总结日志中的关键结论。
包含构建与启动日志摘要、是否存在错误、以及是否可部署的明确判断。
这个数据清洗任务完成后，不要直接说成功。请先运行校验命令或统计检查，确认记录数、空值和格式都符合预期，再汇报结果。
提供校验步骤、关键统计结果，以及数据是否处理成功的结论。
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
| 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 24 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.
帮助你为变量选择清晰准确、易维护的命名，提升代码可读性。
在提交前验证代码变更，并检查是否满足 React 贡献要求。