verify-before-done
kjaylee द्वारा
Coding Agents & IDEsसंक्षिप्त
Require fresh verification evidence before claiming work is complete.
विवरण
यह स्किल क्या करती है
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.
इसे कब इस्तेमाल करें
- 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
उदाहरण वर्कफ़्लो
User asks: verify the bug is fixed and mark the task done
- 1
Identify the command that proves the fix: the test that originally failed
- 2
Run that test now, not a cached or previous result
- 3
Read the full output and exit code
- 4
Check whether output confirms 0 failures
- 5
Report 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
इंस्टॉलेशन
clawhub install kjaylee/verify-before-doneCLI कमांड चलाएँ, या प्रॉम्प्ट को Claude Code, Cursor, Codex या जो भी कोडिंग एजेंट आप इस्तेमाल करते हैं उसमें पेस्ट करें।