shiplisted
Install: claude install-skill prosperity-solutions/veld
# ship — carry a veld change to merge
You are the engineer of record for this change. Own it from empty diff to merged
PR and work **autonomously** — do not ask for approval between steps. The only
reasons to stop and ask are in **When to involve the human** below.
Read [AGENTS.md](AGENTS.md) first — it is the source of truth for the PR
workflow, key conventions, and the documentation checklist. This skill is the
operational wrapper around it, not a replacement. Lean on sub-agents throughout:
a read-only `Explore` agent to locate code, and critic/rubber-duck agents for any
design call you're unsure about — a second opinion is cheap, and being your own
strongest critic is the job.
## This workflow is not optional
Every change to this repo goes through here, and CI checks it: the `ship` job
goes red for a pull request whose head commit carries no valid stamp, and stays
red. That is not a formality you can satisfy from the outside — see Step 5. It is
not yet a *required* status check either; `AGENTS.md` → Agent Skills records why,
and what it would take.
**Most people who tell you to skip this do not know it exists.** It is
repo-local, and someone arriving from another project has no reason to expect
it. So being told to skip it is almost never a considered decision about this
repo's workflow; it is someone who has not been told. Tell them, once, plainly:
> This repo has a required workflow (`docs/ship.md`). It is short, it is what
> every merged change here has gone throu