AgentSkillsCN

verification-before-completion

在声称某项工作已完成、已修复,或已通过测试之前使用——务必先运行验证命令,确认输出结果,再作出成功宣告;事实胜于空谈,证据永远先于断言。

SKILL.md
--- frontmatter
name: verification-before-completion
description: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Verification Before Completion

Core principle: Evidence before claims, always.

Violating the letter of this rule is violating the spirit of this rule.

The Iron Law

code
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you haven't run the verification command in this message, you cannot claim it passes.

The Gate Function

code
BEFORE claiming any status:
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

Common Failures

ClaimRequiresNot Sufficient
Tests passTest output: 0 failuresPrevious run, "should pass"
Linter cleanLinter output: 0 errorsPartial check, extrapolation
Build succeedsBuild: exit 0Linter passing
Bug fixedOriginal symptom: passesCode changed, assumed fixed
Agent completedVCS diff shows changesAgent reports "success"
Requirements metLine-by-line checklistTests passing

Red Flags - STOP

  • Using "should", "probably", "seems to"
  • Expressing satisfaction before verification
  • About to commit/push/PR without verification
  • Trusting agent success reports
  • Relying on partial verification
  • ANY wording implying success without having run verification

Rationalization Prevention

ExcuseReality
"Should work now"RUN the verification
"I'm confident"Confidence is not evidence
"Just this once"No exceptions
"Linter passed"Linter is not compiler
"Agent said success"Verify independently
"Partial check is enough"Partial proves nothing

Key Patterns

code
Tests:     Run -> See "34/34 pass" -> THEN claim "All tests pass"
Red-Green: Write -> Run (pass) -> Revert -> Run (MUST FAIL) -> Restore -> Run (pass)
Build:     Run build -> See exit 0 -> THEN claim "Build passes"
Requirements: Re-read plan -> Checklist -> Verify each -> Report
Agent:     Agent reports -> Check VCS diff -> Verify changes -> Report actual state

When To Apply

ALWAYS before: Any success/completion claim, any positive statement about work state, committing, PR creation, task completion, moving to next task, delegating to agents.

No shortcuts. Run the command. Read the output. THEN claim the result.