Ship.

Workflows

Pipeline behaviour, not YAML brand names

Each card is an intent you implement in GitHub Actions, GitLab, or another scheduler—paired with tools, patterns, and collections that bundle them for real product shapes.

Narrative and screenshots: Use case → ElMundi. Filenames and cron tables: Manual → ElMundi. Manifest source: workflows/manifest.json.

Index

All scheduler intents

Scheduler intents: how cron, PR gates, hosted E2E, self-heal, and audit lanes compose. Behavioural names — YAML filenames differ per org (see reference org manual). 5 entries.

Ship CLI

Workflows commands

Reads workflows/manifest.json from disk — no API. From the Ship repo root (or SHIP_REPO). Explore intent text with ship docs search when the API is up (http://127.0.0.1:8100).

List workflow ids

npm run ship -- workflows list

Print one intent (markdown)

npm run ship -- workflows show pr-and-ci-gate

Semantic search (needs API)

npm run ship -- docs search "PR gate preview" --top-k 6

Tools CLI · Collections CLI · Backend API