smithery.ai

verify

Self-healing verification loop (test → clippy → fmt)

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,764 B
  • docs SUMMARY.md 70 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

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 -- --check

Verification 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.