Individual skill
verification-before-completion
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready. Requires fresh verification output before success claims. Do not use for root-cause debugging, TDD implementation, test-report packaging, or review-feedback triage.
bundled/skills/verification-before-completion/SKILL.md
Source commit bd10381417cbd890ed6f08a18bb18fb5aaf0f741
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,807
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-workflow Repository topic
- automation Repository topic
- codex Repository topic
- developer-tools Repository topic
- skills Repository topic
- ai-skills Repository topic
- claude-code Repository topic
- llm Repository topic
- vibe-coding Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,535 bytes
Read excerpt
# Verification Before Completion
## Overview
Claiming work is complete without verification is dishonesty, not efficiency.
**Core principle:** Evidence before claims, always.
## Routing Boundary
Use this skill at the end of work, when the question is "can we honestly claim this is done?" Use `systematic-debugging` for unexplained failures, `tdd-guide` for test-first implementation, and `generating-test-reports` when the deliverable is a readable test report.
**Violating the letter of this rule is violating the spirit of this rule.**
