← ClaudeAtlas

verifygatelisted

Gate delegated coding work behind a check that can actually fail. Use whenever you are about to hand a task to another coding agent (Codex, a subagent, a teammate), or are writing the verification command for one - it refuses orders with no check, runs the check on the starting state first, and catches the ways a green check hides undone work.
tsurutanmen/claude-plugins · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsurutanmen/claude-plugins
# verifygate Delegate only what a machine can confirm. `pip install git+https://github.com/tsurutanmen/verifygate` ## When to reach for this - You are about to hand a coding task to another agent and are writing the instructions. - You are writing a verification command, a "check the change landed" script, or a CI gate. - Someone reports that a check passed but the work is not actually there. - You are about to run an agent directly in a working copy someone else is using. ## The rule that does the work **No verification command, no delegation.** `verifygate check order.json` exits 2 on an order with no `verify` field. Before writing the order, answer: *what command, run afterwards, would tell me this was done?* If you cannot answer it, the task is not delegable yet. Either find the check first, or do the work yourself. Do not delegate and plan to read the result — reading someone else's code is slower than writing your own. ## Writing the check Three failure modes, in the order they bite: 1. **The check was already green.** Then passing means nothing. Always run it on the starting state first (`verifygate run order.json --dry-run` does this). If it passes there, it does not measure the job. 2. **The check counts, so the agent makes the count right.** "Fewer than N direct colour values" is satisfied by changing what the colours mean. Measure the property you care about, not a proxy for it. 3. **The check asks "is this string present?"** A comment contains