Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Enforces a verification gate before any completion claim, commit, push, PR, or status report. Requires running a fresh command and reading its actual output, exit code, and failure count. Blocks rationalization patterns like 'it should work' or accepting a sub-agent's self-reported success.
It catches the gap between assumption and evidence at the exact moment a false completion claim would otherwise be recorded or communicated.
When to use it
- Confirming tests pass before closing a pull request
- Checking linter output before reporting a clean codebase
- Validating a bug fix by re-running the original failing test
- Auditing a sub-agent's 'success' report with an independent command run
- Ensuring build exit code is 0 before marking a deploy task complete
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: verify the bug is fixed and mark the task done
- 1Identify the command that proves the fix: the test that originally failed
- 2Run that test now, not a cached or previous result
- 3Read the full output and exit code
- 4Check whether output confirms 0 failures
- 5Report completion with the command output as evidence, or report the actual failure if the test still fails
Task marked complete with attached test output showing 0 failures, or honest status report with evidence of remaining failure