$ loading_
Run verification checks before completion to ensure results are truly correct.
The material indicates a prompt-only, open-source skill with no secrets and no remote endpoints, so overall risk is low. The main caveat is limited supply-chain confidence due to low community adoption and unclear license and maintenance status.
The material explicitly states that no keys or environment variables are required; as a prompt-only skill, it does not collect, store, or forward credentials.
The material explicitly lists no remote endpoints, and the system flags it as prompt-only; there is no stated behavior of sending user data to external services.
This skill is behavioral guidance/prompt text and does not include an executable component or claim local process/system access. The README's instruction to 'run verification commands' is guidance to the user/agent, not an execution capability of the skill itself.
No file, directory, database, or other resource access is declared; as prompt-only content, it has no built-in mechanism to read or write local data.
The source is an open GitHub repository, so the contents are auditable, which lowers risk. However, the repo has 0 stars, no declared license, and unknown maintenance status, so community validation and maintenance signals are weak; review the repository before production use.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Verification Before Completion" skill from askskill: 1. Download https://raw.githubusercontent.com/obra/clank/main/skills/debugging/verification-before-completion/SKILL.md 2. Save it as ~/.claude/skills/verification-before-completion/SKILL.md 3. Reload skills and tell me it's ready
I just updated the login module. Before saying the task is done, run the relevant test commands, confirm whether everything passes, and show the key output plus any failures.
A report with test results, pass/fail status, and a completion conclusion based on the output.
Before confirming the app is ready to deploy, run build and local startup verification commands, confirm there are no errors, and summarize the key conclusions from the logs.
A summary of build and startup logs, any detected errors, and a clear readiness-for-deployment decision.
After finishing this data cleaning task, do not claim success immediately. First run validation commands or statistical checks to confirm row counts, null values, and formats match expectations, then report the result.
Validation steps, key statistics, and a conclusion on whether the data processing succeeded.
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.
Compare 2-3 approaches before execution to choose a stronger solution.
Write evergreen comments focused on what and why, not historical context.
Search past Claude Code chats to recover facts, decisions, and context.
Design systems by hiding implementation details behind domain-level interfaces.
Plan with pseudocode first, refine approaches, then translate into working code.
Helps developers keep class abstractions cohesive and free of unrelated responsibilities.
Verify results before claiming work is complete, fixed, or passing.
Provides systematic verification for Claude Code sessions to improve correctness and quality.
Verify AI agent completion claims by checking output file existence and freshness.
Validate code changes before commit and check React contribution requirements.
Run pre-release verification for Django projects across tests, security, and deployment checks.
Helps teams verify deployment readiness, risks, and rollback plans before release.