verification-before-completion
Skill0 starsChanged 6 months agoMITView on GitHub
Self-check before declaring "done" / "ready" / "ship it" on a change. Auto-loads on any code or config edit. User-invocable via /verify. Test-existence is one check among many; this skill enforces sufficiency.
190 other projects use a version of this.
Adopted by
Most recently taken up by
- loganware05/captains-compass-cursortheir own version, first seen Nov 16, 2026
- 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
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 versions190 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 190
- 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
180 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 repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-docs-semanticSkill
- audit-docsSkill
- audit-harness-coverageSkill
- budget-statusSkill
- cavemanSkill
- configurationSkill
- critic-reviewSkill
- doc-patternSkill
- error-taxonomySkill
- grill-meSkill
- grill-with-docsSkill
- new-docSkill
- python-failure-modesSkill
- review-changesSkill
- review-docSkill
- rust-failure-modesSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 178 edited versions we read keep these.
2
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 7
Before saying "done" / "ready for review" / "ship it" on a change, run the verification checklist.
- Distinctive: line 28
Do NOT claim "done" if any item in steps 2–5 is missing.
“Common” is measured: kept by at least 6 in 10 of the 178 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
Before saying "done" / "ready for review" / "ship it" on a change, run the verification checklist. Test-existence hooks enforce that a test exists; this skill enforces that the test exercises the path that changed.
Steps
- Scope check — list every subtree your diff touched (
git diff --name-only). Per-change checklist — for each touched area, verify:
- The change is covered by a test that exercises the new path — not just compiles, not just an unrelated assertion in the same module.
- Error paths in the diff have at least one negative test — happy path alone is insufficient when the change introduces new failure modes.
- State-mutating code — if the change touches mutable state, list the invariants that must hold after the mutation and verify a test asserts each.
- External-boundary code (parsers, deserializers, network ingress) — at least one round-trip or fixture-based test; if property-based, the seed is fixed and recorded.
- Performance-critical code — allocation count unchanged (or the change is justified); no
unwrap()/expect()/panic!introduced in non-test paths. - Configuration — schema validates at startup; new fields either fail loud on absence or have an explicit safe default.
- Test pass status — list which tests ran and which subset relates to the change. "All green" alone is insufficient; identify the specific tests that exercise the modified path.
- Unverified items — explicitly call out any item in step 2 that was NOT verified, with a one-line reason. "Skipped because already covered upstream" is acceptable; "didn't get to it" is not.
- Known-broken — anything left in a known-broken state? Link to a follow-up issue.
Do NOT claim "done" if any item in steps 2–5 is missing.
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.

