Stats
Actions
Tags
From arc
You MUST use this skill before claiming any work is complete, any test passes, or any fix works — especially before arc close, before telling the user "done", or when the user asks "does it work?", "did the tests pass?", "is it fixed?". Requires fresh verification evidence (not cached results). Always prefer this over ad-hoc verification when the project uses arc issue tracking.
How this skill is triggered — by the user, by Claude, or both
Slash command
/arc:verifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run proof commands and read their output before making any completion claim.
Run proof commands and read their output before making any completion claim.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
"It should work" is not evidence. "Tests pass" without output is not evidence. Satisfaction expressed before running the proof command is a red flag.
Create a TodoWrite checklist with these steps:
What command proves the claim? Examples:
make test or go test ./...make buildarc show <id> (check status)Execute the full command. At minimum, run all tests affected by the change; running the full suite is safer. Not a subset from memory. Not "I ran it earlier."
Fresh. Complete. Now.
Read the FULL output. Not just the last line. Check:
Does the output actually confirm the claim?
Make the claim. Reference the evidence:
go test ./... shows 47 passed, 0 failed"make build exits 0, binary at ./bin/arc"You are skipping verification if you:
# ONLY after verification passes:
arc close <id> -r "Verified: <evidence summary>"
If verification fails, do NOT close the issue. Instead:
implement to fix the failuredebug if the failure is unexpectedfinish (session end) or back to implement (next task)skills/arc/_formatting.mdnpx claudepluginhub sentiolabs/agent-nexus --plugin arcEnforces fresh verification evidence before any completion claims, preventing false assertions by requiring commands to be run and output confirmed.
Enforces evidence-based verification by running fresh tests, builds, linters, reviewing outputs before claiming work done, committing, or PRing.
Enforces running verification commands before claiming work is complete. Useful for preventing false success claims and ensuring evidence-based completion.