verificationlisted

Use when about to claim something works, is fixed, or ready to hand off — and when a task changed one or more repos and needs intentional cleanup before stopping. Common triggers: verify, verifiëren, prove, controleren of het werkt, bewijzen dat het werkt, claim success, done, finished, ready, handoff, klaar, gereed, wrap up, hand off, task complete, finishing work, workspace done, afronden, afgerond, inleveren, cleanup, test de fix, check result, prove it works, check of het klopt, validate, valideren, werkt het, is het klaar.
MarkBovee/agent-skills-kit · ★ 1 · AI & Automation · score 72

Install: claude install-skill MarkBovee/agent-skills-kit

# ASK Verification Match the proof to the claim. Bigger claim, stronger evidence. For delegated validation, report `ASK_WORKFLOW_PASS phase=VALIDATE`, `ASK_WORKFLOW_FINDINGS phase=VALIDATE`, `ASK_WORKFLOW_BLOCKED phase=VALIDATE`, or `ASK_WORKFLOW_FAILED phase=VALIDATE` with commands and evidence. Never turn a timeout, missing output, or tool failure into a pass. Validation proves defined technical checks. It does not replace review, independent audit, or release-gate evaluation. ## Verification Match the proof to the claim. Bigger claim, stronger evidence. - **One bug fixed:** reproduce the bug path and show the focused proof now passes - **Feature works:** run targeted tests and exercise the important path - **Ready to merge or hand off:** run the relevant suite, build, or lint checks that cover the touched surface - **Installer or deployer changed:** run the installer into an isolated home and verify the installed copies of user-visible surfaces match the repo, including a refresh over a stale existing install — a green repo-side suite says nothing about what actually got deployed - **Any meaningful code change:** run a proportional smell scan after the main proof. Scan changed files for unbounded loops, sync-over-async, swallowed exceptions, missing cancellation, duplicated I/O or N+1 queries, hardcoded configuration, runtime artifacts, silent unknown-event handling, and relevant test gaps. Expand to a repository-wide scan for cross-module changes, audits, or explici