verify
Skill196 starsChanged 13 days agoMITView on GitHub
Self-healing verification loop (test → clippy → fmt)
189 other projects use a version of this.
Adopted by
Most recently taken up by
- Automattic/wp-calypsotheir own version, first seen Nov 16, 2026
- abe238/hotinaitheir own version, first seen Nov 16, 2026
- SmartStudio/baize-bottheir own version, first seen Nov 15, 2026
- YuBan834/vrma-labtheir own version, first seen Nov 15, 2026
- Ju571nK/lodelinetheir own version, first seen Nov 15, 2026
- ericbust/namedroptheir own version, first seen Nov 15, 2026
Used with
Projects with it also use genie-hacks, workfly 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.
automagik-devSkillgenie-hacks
Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.
Also in 3 projects that use this
automagik-devSkillworkfly
Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.
Also in 3 projects that use this
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
AviadPSkillrisk-assess
Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 6 projects that use this
- +2 more from automagik-dev
- +1 more from TheKREATORS
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- react/react★ 253ksame name
- facebook/react★ 253ksame name
- garrytan/gstack★ 142ksame name
- oven-sh/bun★ 97ksame name
- anthropics/financial-services-plugins★ 41ksame name
- anthropics/financial-services★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- anthropics/claude-quickstarts★ 19ksame name
- NVIDIA-NeMo/Speech★ 19ksame name
179 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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Do not use a merely written test as evidence of "confirmed" (false-green = false reassurance).
- Distinctive: line 37
If a path is covered only by mocks, report it as "mock coverage only — integration unconfirmed" rather than "verified".
- Very specific: line 40
Read the PLAN Acceptance/DoD and any [unverified-gate] passed from implement.
- Very specific: line 41
If unrunnable (prod smoke / external service / CI-only environment) → no green-wash.
- Distinctive: line 56
All must pass to proceed
- Distinctive: line 61
If there are unresolved BLOCKERs, do not proceed to /review — report "verification incomplete + reason + required environment actions" to …
“Common” is measured: kept by at least 6 in 10 of the 168 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
Verify
Flow
cargo test → cargo clippy → cargo fmt --check
│ │ │
└── On fail: fix and retry (notify user after 3 same failures)Commands
cargo test --quiet
cargo clippy --all-targets --all-features -- -D warnings
cargo fmt --all -- --checkVerification Honesty (MUST — PASS gate)
Verification trustworthiness lies not in "what passed" but in "what was actually executed and passed". Enforced before any PASS verdict.
Skip ≠ Pass
- Tests marked
ignored/#[ignore]are unverified → do not count as green. - Tests skipped due to environment (missing external service, platform constraints, etc.) are a BLOCKER. If unfixable, escalate to user as "verification incomplete + reason" rather than PASS.
Do not cite unrun tests as verification evidence
- "Confirmed via test X" is only valid when that test actually ran and passed in this execution.
- Do not use a merely written test as evidence of "confirmed" (false-green = false reassurance).
Coverage honesty (mock ≠ real)
- Mock-based unit tests verify only the logic inside the mock boundary. Behaviors invisible to mocks — file I/O, concurrency, simd-json real parsing — are confirmed only by integration verification.
- If a path is covered only by mocks, report it as "mock coverage only — integration unconfirmed" rather than "verified".
Acceptance/DoD cross-check (carry PLAN gates)
- Read the PLAN Acceptance/DoD and any
[unverified-gate]passed from implement; cross-check whether each item actually ran and passed in this execution. - If unrunnable (prod smoke / external service / CI-only environment) → no green-wash. Tag as
[unverified-gate: delegated, owner/due/probe]and carry to wrap Plan Reconciliation (../wrap/references/reconciliation.md).
Report format
- ✅ Actually executed and passed
- ⛔ Skipped/environment-blocked + reason (unresolved = BLOCKER, not PASS)
- ⚠️ Mock coverage only, integration unconfirmed
- ⏳ Delegated to wrap due to unverifiable Acceptance item
Self-Healing
- Fail → analyze error → fix code → retry
- Same error 3 times → notify user
Rules
- Required before commit
- Order: test → clippy → fmt
- All must pass to proceed
Next Step
Only when the Verification Honesty gate passes (actual execution passed, no unresolved BLOCKERs) → call /review immediately. Do not ask "should I review?".
If there are unresolved BLOCKERs, do not proceed to /review — report "verification incomplete + reason + required environment actions" to the user.
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.

