trust-but-verify

Validates completion claims by running project verify commands before done assertions.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill trust-but-verify-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trust-but-verify
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/trust-but-verify
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill trust-but-verify-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI assistants and developers often claim work is done, fixed, or working based on stale test runs or assumptions, leading to broken code being pushed, PRs opened on failing builds, and unverified handoffs. This Skill enforces an evidence gate: no completion claim is permitted without a fresh run of the project's verify command and a zero exit code. ## Core Features & Use Cases - Evidence Gate: Blocks done/works/fixed claims, git push, PR creation, and session handoffs until the verify command runs fresh and exits 0. - Automatic Verify Command Detection: Resolves the right command via a priority chain — explicit declaration in CLAUDE.md/KNOWLEDGE.md, Makefile/justfile targets, package.json scripts, CI workflow run steps, or tool-presence fallback (bats, shellcheck, pytest, cargo, go). - Accountability Tracking: Converts unproven claims into Critical [VERIFY] TODOs in TODOS.md, routes test failures to [TEST]/[BUG] workflows, and writes [UX] checklists for machine-unverifiable results. - Use Case: Before pushing a bug fix, the gate runs bats --tap tests/ fresh, reads exit 0 with 82 passing tests, and only then permits the claim — citing the evidence. ## Quick Start Ask the AI to verify the current changes with the project's verify command before claiming the fix is done.

Frequently Asked Questions about trust-but-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes before claiming a task is done?▼

Run the project's verify command fresh after your last edit and read the exit code. Exit 0 permits the claim with cited evidence; a non-zero exit means fix the issue or record a [VERIFY] TODO instead of claiming completion.

How is the verify command detected for a project?▼

Detection follows a priority chain: explicit declaration in CLAUDE.md or KNOWLEDGE.md, then Makefile/justfile test or check targets, package.json scripts, CI workflow run steps, and finally tool-presence inference for bats, shellcheck, pytest, cargo, or go.

Does the verification gate run before every git commit?▼

No, the gate explicitly does not fire before commits because commits are cheap work-in-progress checkpoints. It fires before done claims, git push, PR creation, and handoffs to users or subagents.

What happens when a claim cannot be verified automatically?▼

Machine-unverifiable results like visual output or UX flows are not marked done and do not loop on [VERIFY]. Instead a [UX] checklist with steps and success criteria is written and handed off to the user for manual confirmation.

What if no verify command can be resolved for a project?▼

The Skill reports this honestly and recommends adding a one-line verify command declaration to the project's CLAUDE.md or KNOWLEDGE.md. Until then, all completion claims are treated as unproven.