verification-before-completion

Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "verification-before-completion" with this command: npx skills add izyanrajwani/agent-skills-library/izyanrajwani-agent-skills-library-verification-before-completion

Verification Before Completion

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

Core Protocol

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

BEFORE any completion claim:
1. IDENTIFY: What verification 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?
   - NO → State actual status with evidence
   - YES → State claim WITH evidence
5. ONLY THEN: Make the claim

Command Selection

When multiple verification options exist (mono-repo, multiple suites):

  • Run the most specific command that covers the changed code
  • When uncertain, run the broadest command (full test suite > single file)
  • Lint ≠ build ≠ test — each verifies different claims

Evidence Format

✅ Ran: npm test
   Exit: 0
   Result: 47 passed, 0 failed
   "All tests pass."

❌ "Tests should pass now" (no command output)

Verification Requirements by Claim Type

ClaimRequired EvidenceInsufficient
Tests passTest output: 0 failuresPrevious run, "should pass"
Linter cleanLinter output: 0 errorsPartial check, extrapolation
Build succeedsBuild exit code: 0Linter passing
Bug fixedOriginal symptom test passesCode changed
Regression testRed-green cycle verifiedSingle green
Agent completedVCS diff shows changesAgent "success" report
Requirements metLine-by-line checklistTests passing

Red Flags — STOP

  • Words: "should", "probably", "seems to"
  • Satisfaction before verification: "Great!", "Perfect!", "Done!"
  • About to commit/push/PR without verification
  • Trusting agent success reports
  • Partial verification
  • ANY wording implying success without verification output

Rationalization Prevention

ExcuseResponse
"Should work now"Run the verification
"I'm confident"Confidence ≠ evidence
"Just this once"No exceptions
"Linter passed"Linter ≠ build
"Agent said success"Verify independently
"Partial check enough"Partial proves nothing

Key Patterns

Tests:

✅ [Run test] → [See: 34/34 pass] → "All tests pass"
❌ "Should pass now"

Regression (TDD):

✅ Write → Run (pass) → Revert fix → Run (MUST FAIL) → Restore → Run (pass)
❌ "Wrote regression test" (no red-green)

Requirements:

✅ Re-read plan → Checklist each item → Report gaps or completion
❌ "Tests pass, phase complete"

Agent delegation:

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

systematic-debugging

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

executing-plans

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

writing-skills

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

writing-plans

No summary provided by upstream source.

Repository SourceNeeds Review