Verification before completion
Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/codingcossack/verification-before-completion
π§ The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill verification-before-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
3.0 KB, 684 tokens by cl100k_base, as published. Nobody here has run it
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
| Claim | Required Evidence | Insufficient |
|---|---|---|
| Tests pass | Test output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build exit code: 0 | Linter passing |
| Bug fixed | Original symptom test passes | Code changed |
| Regression test | Red-green cycle verified | Single green |
| Agent completed | VCS diff shows changes | Agent "success" report |
| Requirements met | Line-by-line checklist | Tests 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
| Excuse | Response |
|---|---|
| "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
Gives 2 of the 12 instructions most quality gates skills give in 684 tokens
Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-06
- read the output and check the exit codehere, and in 55 of 1195, across 14 files
- verify requirements using a line-by-line checklisthere, and in 53 of 1195, across 12 files
- identify the verification command proving the claimin 53 of 1195, across 12 files
- run the full verification commandin 51 of 1195, across 11 files
- verify output confirms the claimin 49 of 1195, across 10 files
- check version control diff after agent delegationin 45 of 1195, across 5 files
- state claim with evidencein 43 of 1195, across 3 files
- run the test suitein 32 of 1195, across 24 files
- keep state in memory by defaultin 27 of 1195, across 6 files
- make prototype runnable with one commandin 26 of 1195, across 5 files
- detect the package manager from lockfilesin 24 of 1195, across 5 files
- produce a verification reportin 23 of 1195, across 12 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.