verification-before-completion
Skill2 starsChanged 36 days agoMITView on GitHub
Use before claiming work is complete, fixed, or passing — require fresh verification command output in-session before any success claim
189 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Badhon-00/MDCPtheir own version, first seen Nov 16, 2026
- dragoshont/architravetheir own version, first seen Nov 16, 2026
- matt-riley/agent-skillstheir own version, first seen Nov 15, 2026
- Binbin-miao/workbuddy-expert-teamtheir own version, first seen Nov 15, 2026
- Aliolabadiena/sonelletheir own version, first seen Nov 15, 2026
- mintunitish/tandemtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
obraSkilldiagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Also in 20 projects that use this
jh941213Skilldocs-ci
문서 CI(링크·OpenAPI lint·breaking 게이트·mermaid 검증)나 문서 드리프트 감지(docs.yaml 신선도 검사)를 설치하거나 돌릴 때 사용. 문서 내용 작성은 docs-architecture·docs-interfaces·docs-manuals.
Also in 3 projects that use this
jh941213Skilldocs-interfaces
API·이벤트 인터페이스 문서(OpenAPI·swagger·AsyncAPI 명세, 엔드포인트 레퍼런스, API 구성도·시퀀스, API CHANGELOG)를 만들거나 코드와 맞출 때 사용. 시스템 구성도는 docs-architecture, API 설계 원칙은 api-design-principles.
Also in 3 projects that use this
- +3 more from Leodorareluctant259
- +4 more from jh941213
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Saddss/cursor-skills★ 211% same
Wrote their own version · 188
- obra/superpowers★ 314ksame name
- jnMetaCode/superpowers-zh★ 8.5ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- lingyired/status-trio★ 1.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
- DemonDamon/AgenticX★ 1ksame name
- mdiri-ai/SoduWork★ 930same name
- coco-research/coco★ 797same name
178 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-core-operating-model.mdcCursor rule
- .cursor/rules/01-plan-approval-gate.mdcCursor rule
- .cursor/rules/02-git-worktree-policy.mdcCursor rule
- .cursor/rules/03-validation-definition-of-done.mdcCursor rule
- .cursor/rules/04-documentation-memory.mdcCursor rule
- accessibility-reviewSkill
- agent-skills-packagingSkill
- autonomy-budgetSkill
- bounded-autonomySkill
- candidate-promotionSkill
- capability-planningSkill
- code-reviewerSkill
- code-structure-cleanupSkill
- compass-evaluatorSkill
- context-inodesSkill
- dependency-supply-chainSkill
- design-before-planSkill
- docker-cloudSkill
- embedding-providersSkill
- execution-telemetrySkill
- experience-routingSkill
- experience-skill-trainingSkill
- external-knowledge-ingestSkill
- finishing-a-development-branchSkill
- github-integrationSkill
- goose-agent-orchestrationSkill
- harness-gcSkill
- hosted-vector-dbSkill
- implementation-planningSkill
- ios-engineeringSkill
- knowledge-stewardSkill
- linear-integrationSkill
- node-engineeringSkill
- northstar-connected-routineSkill
- notion-integrationSkill
- package-registry-tiSkill
- persistent-role-promotionSkill
- playwright-browser-validationSkill
- postgres-prismaSkill
- post-merge-wave-continueSkill
- procedure-playbooksSkill
- project-overseerSkill
- pull-request-preparationSkill
- python-mlSkill
- react-engineeringSkill
- repository-discoverySkill
- review-fix-loopSkill
- security-audit-proceduresSkill
- security-reviewSkill
- skill-learning-loopSkill
- skill-lifecycleSkill
- source-code-contextSkill
- subagent-driven-developmentSkill
- technology-intelligence-liveSkill
- testing-validationSkill
- worktree-orchestrationSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 177 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Before committing “validation done”, opening a PR, or declaring Definition of Done
- Distinctive: line 24
If you have not run the verification command in this turn (or attached its fresh output), you cannot claim it passes.
- Distinctive: line 54
Do not claim green without a fresh run in-session
- Distinctive: line 55
Do not weaken, delete, or skip failing tests to force a pass
- Distinctive: line 56
Do not treat chat memory of an older run as evidence
“Common” is measured: kept by at least 6 in 10 of the 177 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verification Before Completion
Patterns inspired by obra/superpowers
verification-before-completion (DISCOVERED inspiration — not a plugin install).
Aligns with always-on rule 03-validation-definition-of-done.
Use this Skill when
- About to claim tests pass, a bug is fixed, build succeeds, or work is complete
- Before committing “validation done”, opening a PR, or declaring Definition of Done
Iron law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCEIf you have not run the verification command in this turn (or attached its fresh output), you cannot claim it passes.
Inputs
- The exact claim you want to make
- Project test / doctor / build commands from
TESTING.md
Procedure
- IDENTIFY the command that proves the claim.
- RUN the full command fresh (not a remembered earlier result).
- READ exit code and full relevant output; count failures.
- VERIFY the output actually supports the claim.
- ONLY THEN state the claim with evidence (command + result summary).
- Store transcripts under
.agent/evidence/when this is a plan closeout.
| Claim | Requires | Not sufficient |
| Tests pass | Test command: 0 failures | “Should pass”, prior run |
| Doctor clean | ./scripts/doctor.sh exit 0 | Partial check |
| Bug fixed | Repro or failing test now passes | Code changed only |
| Agent finished | Diff / evidence matches acceptance | Agent said “done” |
Output
Claim paired with fresh command evidence, or an honest failure report.
Prohibited actions
- Do not claim green without a fresh run in-session
- Do not weaken, delete, or skip failing tests to force a pass
- Do not treat chat memory of an older run as evidence
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

