Prove It — evidence before "done" (repo-agnostic)

Overview

Features have passed build + typecheck + tests + review + deploy and still been dead in production, because no gate ever exercised the real write. Green checks measure what the checks measure — this skill measures whether the feature works. It ends in a table where every claim carries the command that proves it.

If the current repo has its own .claude/skills/prove-it/ or .agents/skills/prove-it/, that version is authoritative — follow it instead. This global version is the fallback.

Announce at start: "Running /prove-it verification."

The rule underneath every step: a claim without a command is labeled UNVERIFIED in the final table. An honest UNVERIFIED outranks a confident guess.

Step 0: Discover what CI actually gates

Read the repo's CI workflows once (.github/workflows/). Many repos gate far less than their green checks imply — lint-only PR gates are common, and some builds skip type-checking (ignoreBuildErrors). Everything CI does NOT run, you run locally.

Step 1: Both static gates

Run the typecheck AND the build — neither substitutes for the other (builds catch bundler/route/import errors types miss; typecheck catches what a lenient build ignores). If the repo tracks a baseline error count, compare against it and state both numbers.