Verify agent completion claims against git ground truth
Verifies AI agent done-claims by checking git diffs and commit ancestry with the DOS kernel, replacing self-reports with deterministic, offline git-only
17.4.0Add to Favorites
Why it matters
Ensure AI agent claims of "done," "shipped," or "fixed" are factually grounded by validating them against actual git commit history and diffs using the deterministic DOS kernel, replacing unreliable self-reports with witness-based verification.
Outcomes
What it gets done
Shell the DOS kernel to verify claimed changes against git ancestry
Audit commit diffs to confirm the agent's stated effects actually occurred
Replace agent self-consistency checks with external ground-truth validation
Run offline, deterministic git-only verification without LLM or API calls
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-dos-verify-done-claims | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Overview
Verify done-claims against ground truth, not the agent's word
This skill shells the DOS kernel to verify AI agent done-claims by checking git commit ancestry and diffs. Instead of accepting an agent's self-report, it uses `dos verify` and `dos commit-audit` to produce a deterministic, git-only verdict. DOS is deterministic and operates offline without API keys or LLM calls. Use this skill when you need auditable proof that an AI agent's claimed code changes actually exist in git history. It is essential for workflows where agent completion status must be verified against external artifacts rather than the agent's own consistency checks.
What it does
This skill replaces AI agent self-reports with deterministic verification from an independent witness. When an agent claims "done", "shipped", or "fixed", this skill shells the DOS kernel (dos verify, dos commit-audit) to confirm the claimed effect by examining git ancestry and the commit's actual diff. The verdict comes from git history, not from the agent re-reading its own work.
When to use - and when NOT to
Use this skill when you need to validate that an AI agent's claimed changes actually exist in the git commit history and match the stated effect. It is essential when agent claims must be auditable and when you cannot trust self-reported completion status. Use it in workflows where deterministic, offline verification is required without API keys or LLM calls.
Do NOT use this skill if you need real-time CI oracle integration without suppression flags, as dos verify in a workspace wired to a CI oracle will contact external services unless you pass --no-ci.
Inputs and outputs
You provide the agent's done-claim and access to the git repository where the claimed changes should exist. The skill shells DOS kernel commands against the repository to audit commits.
You receive a deterministic verdict based on git-only evidence: whether the commit ancestry and diff confirm the agent's claim.
Integrations
DOS kernel: the deterministic verification engine used for git repository verification. DOS is offline by default. When a workspace wires a CI oracle, dos verify can contact external CI services unless suppressed with the --no-ci flag.
Who it's for
This skill is for developers and teams who deploy AI agents in code-modification workflows and require auditable proof that claimed changes actually landed in version control. It is particularly valuable for users who prioritize deterministic, offline verification over LLM-based validation.
Source README
When an AI agent says "done", "shipped", or "fixed", that is a claim, not a
fact - and a claim the agent checks by re-reading its own work is consistency,
not grounding. This skill replaces that self-report with a verdict from a
witness the agent did not author: it shells the DOS kernel (dos verify,dos commit-audit) to confirm the claimed effect from git ancestry and the
commit's actual diff. DOS is deterministic - no API key, no LLM. The verdict is
git-only and offline as used here; the one exception is dos verify in a
workspace that wires a CI oracle, which --no-ci suppresses (see Security &
Safety Notes).
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.