Tools
Integrations your stack actually runs
This section lists concrete surfaces — Linear, GitHub Actions, Playwright, Cursor Cloud Agent, local Chroma search, the methodology HTTP API, and supporting contracts. Each card opens markdown in this repo (same idea as org patterns, but here the focus is tooling, not SDLC prompt slices).
Neutral core
Capabilities, not brands
Ship standardizes interfaces between tracker, scheduler, agent runtime, regression runner, and security signal. Vendors swap; receipts stay legible.
Git-first
Manifest + markdown
tools/manifest.json indexes files under documentation/tools/. Improve the text with normal PRs — the site is a reader.
Automation
Same HTTP API
Agents still call POST /search and POST /fetch with repo-relative paths when they need full bodies after discovery.
How to use this section
- 1
Pick the integration you are wiring
Start from Capability map if the team argues about scope, then open Linear, Actions, Playwright, or Cursor Cloud for the specifics.
- 2
Fork and rename for your org
ElMundi names in the manual are reference only; your URLs, projects, and secrets differ. The contracts here stay portable.
- 3
Drive agents from the API + patterns
Pair this list with org patterns and the Backend API doc — search, fetch, then execute role prompts.
Story and evidence: Use case → ElMundi. YAML names and minutes: Manual → ElMundi · on GitHub: tools/manifest.json.
Index
Every integration surface
Surfaces agents and humans wire together: tracker, CI scheduler, E2E runner, cloud agent host, local embeddings search, and the methodology HTTP API. Currently 9 entries.
- Platform & API
Five capabilities
Neutral map of what a Ship-style setup needs — no vendor lock-in in the names.
maparchitecture - Tracker
Linear
Tracker as system of record — projects, states, labels, evidence for agents.
graphqlprojectsstates - Tracker
Tracker contract
Vendor-neutral shape: states, labels, evidence — Linear, Jira, GitHub Issues, or spreadsheets.
abstractionstateslabels - CI & scheduler
GitHub Actions
Cron, concurrency, workflow_dispatch, artifacts as the audit trail.
yamlschedulersecrets - E2E
Playwright
Hosted regression — pinned URLs, artifacts, flake vs defect triage.
browserartifactsflake - Agents
Cursor Cloud Agent
Cloud runtime — PR contract, secrets mirroring, prompts versioned in git.
branchprruntime - Platform & API
Chroma (local)
On-disk vector index for POST /search over docs and prompts.
embeddingslocalindex - Platform & API
Methodology API
FastAPI for agents; humans use ship docs / ship patterns CLI against the same routes.
httpfastapiagents - Platform & API
Snyk
Dependency and security signal — triage with agents and release gates.
dependenciessca
Ship CLI
Tools commands
List and show read tools/manifest.json from disk — no API server. Run from the Ship repo root (or set SHIP_REPO). Semantic search still uses the methodology API — start uvicorn first; base URL defaults to http://127.0.0.1:8100 (--base-url / SHIP_API_BASE).
List tool ids
npm run ship -- tools list
Print one tool doc (markdown)
npm run ship -- tools show playwright
Semantic search (needs API)
npm run ship -- docs search "Playwright hosted regression" --top-k 6
Fetch arbitrary path (needs API)
npm run ship -- docs fetch documentation/tools/integrations/playwright.md
Raw HTTP: Manual → Backend API · Patterns CLI · Companion API