From beislid
Enforces running fresh verification commands like tests, linters, or builds and reading output before claiming work is complete, fixed, or passing. Prevents unsubstantiated assertions.
npx claudepluginhub sandsower/beislidThis skill uses the workspace's default tool permissions.
No completion claims without fresh verification evidence. Period.
Enforces fresh command output verification before claiming task completion, bug fixes, test passes, builds, deployments, or success.
Enforces running verification commands before claiming tests pass, builds succeed, bugs fixed, or work complete. Ensures evidence-based status reports.
Enforces running verification commands for tests, linters, builds before claiming work complete, fixed, or passing; requires fresh output evidence prior to commits/PRs.
Share bugs, ideas, or general feedback.
No completion claims without fresh verification evidence. Period.
Before ANY claim that work is done, tests pass, a bug is fixed, or code is working — you MUST run the verification command, read the output, and confirm it matches the claim.For every positive claim about work state:
| Claim | Required evidence |
|---|---|
| "Tests pass" | Test command output showing 0 failures |
| "Linter clean" | Linter output showing 0 errors |
| "Build succeeds" | Build command with exit code 0 |
| "Bug is fixed" | Failing test now passes (red to green) |
| "Feature works" | Test or manual verification output |
These words in your response without preceding evidence mean you're guessing:
Replace with: run the command, paste the output, state the fact.
Agent success reports are not evidence. After a subagent completes:
If the user explicitly asks for a richer visual proof deck, invoke show-me. If verification would be clearer as screenshots, videos, diffs, command logs, or a browsable HTML report, suggest show-me and wait for a direct user request. Do not run show-me automatically; it is a manual/user-requested escalation in v1.