AgentSkillsCN

verification-before-completion

适用于即将宣布某项工作已完成、修复完毕或测试通过时使用——在提交代码或创建 PR 之前，务必先运行验证命令并确认输出结果，再作出任何成功宣告；事实胜于空谈，证据永远先行。

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

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

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 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

Common Failures

ClaimRequiresNot Sufficient
Tests passTest command output: 0 failuresPrevious run, "should pass"
Linter cleanLinter output: 0 errorsPartial check, extrapolation
Build succeedsBuild command: exit 0Linter passing, logs look good
Bug fixedTest original symptom: passesCode changed, assumed fixed
Regression test worksRed-green cycle verifiedTest passes once
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 ("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

Rationalization Prevention

ExcuseReality
"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

Key Patterns

Tests:

code
✅ [Run test command] [See: 34/34 pass] "All tests pass"
❌ "Should pass now" / "Looks correct"

Regression tests (TDD Red-Green):

code
✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "I've written a regression test" (without red-green verification)

Build:

code
✅ [Run build] [See: exit 0] "Build passes"
❌ "Linter passed" (linter doesn't check compilation)

Requirements:

code
✅ Re-read plan → Create checklist → Verify each → Report gaps or completion
❌ "Tests pass, phase complete"

Agent delegation:

code
✅ Agent reports success → Check VCS diff → Verify changes → Report actual state
❌ Trust agent report

Why 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."

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

BuildStream-Specific Verification

Element changes require a local build log. This is a hard gate -- no exceptions.

Change TypeRequired Verification
New or modified .bst elementjust bst build <element> -- show output with exit 0
Changes affecting the OCI imagejust build -- full image build, show output
Removing an elementjust build -- confirm image still builds without it
Patching a junction elementjust bst build <affected-element> for each affected element
Updating an upstream refjust build -- full image build (ref changes can cascade)

What "show output" means: The build command's stdout/stderr must appear in the conversation. A summary like "it built successfully" is NOT sufficient -- paste the actual terminal output showing the build completed.

Rationale: CI takes 30-60 minutes. Local builds with a warm cache take minutes. Catching failures locally is faster, cheaper, and more respectful of shared CI resources. See local-e2e-testing skill for build commands.

Rule applies to:

  • •Exact phrases
  • •Paraphrases and synonyms
  • •Implications of success
  • •ANY communication suggesting completion/correctness

The Bottom Line

No shortcuts for verification.

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

This is non-negotiable.