verification-before-completion

Installation
SKILL.md

Verification Before Completion

Purpose

Ensure every claim that work is complete, fixed, or passing is backed by fresh, observed verification evidence — never by intent, code inspection, memory, or output from before the last change.

Workflow

  1. Name the exact claim you are about to make and the command that would prove it: the project's test suite, build, linter, or the original reproduction.
  2. Check whether the user explicitly authorized that covered operation in the current conversation. Run the command fresh, in this turn, after the final change, only when authorized. If it is not authorized, do not run it; report status: unverified and name the exact verification gap.
  3. Read the actual output when a command runs. Confirm the exit code and the expected success markers; a truncated, partial, or misread run is not evidence.
  4. If verification fails, or the command cannot run, downgrade the claim and state the blocker. Never claim success because the change "should" work.
  5. Only then report status, citing the command that was run and its observed result, or the missing authorization and resulting gap.

Output Contract

Return exactly these fields:

Installs
4
First Seen
Oct 13, 2026