DoneCheck makes AI coding agents leave proof before saying done

DoneCheck is a small open-source tool for such as Codex, Claude Code, and Cursor. It is available as a Python and a . It checks changed files, runs the command chosen by the developer, and records the result.

If there is no proof of , it fails the run and writes a DONECHECK.md receipt with the changed files, command, exit code, and recent output. It is also meant to catch common AI coding misses such as TODO placeholders, skipped checks, stale receipts, and hidden exceptions. Related safety tools such as Bouncer point to the same wider need: AI agents need guardrails before developers trust their changes or let them run risky .

The practical shift is from accepting an agent’s “done” message to requiring visible evidence that the work was checked.

Key points

  • DoneCheck is an open-source proof gate for .
  • It scans changed files, runs a chosen command, and writes a DONECHECK.md receipt.
  • It can fail when there is no evidence or when obvious AI-code issues appear.
  • It can be used locally as a Python or in workflows.
  • The broader trend is safer AI coding workflows with proof, logs, and guardrails around risky commands.

Sources covering this story (9)

Read original