# Prove It Ship Gate

> Auto-trigger when claiming a feature, worker, or integration is done, shipped, or working and the Goal includes live side effects (Linear tickets, deploy, live mine, external APIs). Unit/fixture tests and UI registration alone are not enough — route to prove-it for live evidence before treating the claim as settled.

- Skill: `edbertchan/prove-it-ship-gate` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add edbertchan/prove-it-ship-gate`
- Raw SKILL.md: https://api.skillmd.com/api/skills/edbertchan/prove-it-ship-gate/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: EdbertChan (https://skillmd.com/u/edbertchan)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/edbertchan/prove-it-ship-gate

---


# prove-it-ship-gate

Thin routing skill for ship/done claims with live side effects.

Follow Invoker or a locally installed `prove-it` for the shared evidence rule.
This file only adds the ship/done auto-route; it does not replace `prove-it`.

## Rule

When the work under claim has live side effects:

- **Fixture ≠ live.** Unit tests, mocked fixtures, and UI registration Visual
  Proof do not prove the live path ran.
- Before stating done / shipped / working: show **live evidence in the same
  turn**, or prefix the claim with `UNVERIFIED: live path`.
- Do not frame UI Visual Proof (for example worker registration in a settings
  panel) as product e2e of the live side effect.

## Mechanical enforcement

The same-turn check is a Stop hook, `engine/hooks/prove-it-ship-gate/`
(installed by `install.sh`). It blocks the turn when a done/shipped/live claim sits
near a live-side-effect noun with no chaseable evidence, no live command this turn,
and no `UNVERIFIED: live path` prefix. This file keeps the judgment half: deciding
whether the work really has live side effects.

## Incident

Invoker PRs #10553–#10558 published cross-repo-research after unit + fixture +
UI only; the user forced a live Linear e2e and a reflect afterward.

## Related

If the claim isn't done/shipped but repeated failed attempts on one problem within a live session, that's `narrow-the-scope`, not this skill.

If a grading/validation board came back FAIL or NEEDS_WORK, or the user says "/thrash", that's `thrash-reflect-automate`.