/verify
Self-healing verification loop (test → clippy → fmt)
$ npx -y skills add mag123c/toktrack --skill verify --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/verify
Context preview
The summary Claude sees to decide when to auto-load this skill.
Self-healing verification loop (test → clippy → fmt)
SKILL.md
verify.SKILL.mdname: verify
description: Self-healing verification loop (test → clippy → fmt)
required_context: []
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.
Read more
name: verify description: Self-healing verification loop (test → clippy → fmt) required_context: []
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.
Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code)
Other skills on toktrack.
- /clarify
Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.
Open skill - /implement
TDD implementation (RED→GREEN→REFACTOR) → verify → review
Open skill - /next
Session start - check progress, suggest next task
Open skill - /review
Multi-agent code review for Rust CLI/TUI. UX Review inactive (terminal UI — no web frontend). Code Review only. Includes Rust/clippy-specific checklist.
Open skill - /wrap
Session end - document updates, commit
Open skill

