dos-verify-done-claims

Verify agent completion claims against git history and commit diffs.

18|4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-verify-done-claims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dos-verify-done-claims
Source: https://github.com/anthony-chaudhary/dos-kernel/tree/main/listings/antigravity-skill
Command: npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill dos-verify-done-claims

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an AI agent says a task is done, shipped, or fixed, you need evidence from git instead of a self-report. This Skill turns completion claims into a verifiable verdict so false finishes do not get accepted.

Core Features & Use Cases

  • Commit audit: Compare a commit message with its actual diff to see whether the claimed change is supported.
  • Phase verification: Check whether a named plan, feature, or phase has truly shipped in repository history.
  • Quality gate: Block done status until DOS confirms the claim from ground truth.
  • Use case: An agent says it fixed a bug, but the commit only updates documentation; this Skill flags the claim as unproven.

Quick Start

Ask the agent to verify the claimed feature or fix with DOS before you accept it as done.

Frequently Asked Questions about dos-verify-done-claims

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

FAQPage Schema
How do I verify AI agent done claims against git history?

Verifying AI agent done claims requires running deterministic read-only DOS checks against git ancestry and commit diffs to produce evidence-based verdicts. This compares the agent's completion statement with actual repository changes to catch false finishes.

What is a git commit audit for AI agents?

A git commit audit compares an AI agent's commit message with its actual diff to determine whether the claimed change is supported by the code. It flags discrepancies, such as an agent claiming a bug fix while only updating documentation.

How do I set up a quality gate to block false done claims in git?

To block false done claims, integrate a deterministic verification step into your quality gate that requires DOS confirmation from git ground truth before accepting a done status. This prevents unproven completion claims from passing phase-shipment checks.

Can I check if a named feature phase has truly shipped in repository history?

Yes, phase verification checks whether a named plan, feature, or phase has truly shipped by examining repository history. It applies read-only DOS verification against git ancestry to provide an evidence-based provenance verdict.

Does git commit verification work without modifying repository state?

Yes, DOS verification is strictly deterministic and read-only, meaning it examines git ancestry and commit diffs without modifying repository state. It safely provides evidence-based verdicts for commit audits and phase-shipment checks.

When should I use commit audits instead of trusting agent self-reports?

Use commit audits whenever an AI agent reports completed work in repositories where accuracy is critical. Audits replace self-reports with ground truth from git diffs, catching unproven claims before they are accepted as done.