heliohq/ship/use-ship

Claude Code and agent skill by heliohq/ship

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Route ambiguous software-delivery requests to the smallest useful Ship workflow: one skill, a phase bundle, or /ship:auto. Use at session start, when the user asks how to use Ship, or when they say build/check/ship without a phase.

Install

npx vskill@latest install heliohq/ship/use-ship

SKILL.md

Ship: Use Ship

Choose the smallest useful Ship workflow for the request, state the route briefly, then invoke the matching skill(s). Each skill's own description is the primary routing signal — this file only settles the ambiguous cases. Do not force the full pipeline unless the user explicitly wants production delivery.

Routes

NeedRoute
Understand scope, write a plan, de-risk approach/ship:design
Architecture/API/data-model decision, ADR, trade-off analysis/ship:arch-design (thinking) → /ship:write-docs (record), then /ship:design if implementation follows
Implement a well-scoped change/ship:design → /ship:dev
Implement from an existing approved plan/ship:dev
Add durable browser/API/CLI coverage/ship:e2e
Check code correctness/ship:review
Verify runtime behavior/ship:qa
Harden a completed change/ship:e2e → /ship:review → /ship:qa → /ship:refactor
Prepare delivery after work is complete/ship:handoff
End-to-end production delivery (explicit ask only)/ship:auto

Ambiguous phrasings default to a bounded bundle, never the full pipeline: "plan this" → design; "build this" → design → dev; "check this change" → review and/or qa; "make this production-ready" → the hardening bundle; "ship this all the way" → auto.

Boundaries

  • Standalone: atomic skills work without /ship:auto or any task

directory. If the user names a phase, run that phase directly.

  • State: during full flows, raw input lives at

.ship/tasks/<task_id>/input/requirement.md; orchestrator state is minimal and orchestrator-owned. Markdown artifacts and repository code are the real deliverables.

  • Durable production artifacts: use the repository's existing

convention first; otherwise create only the needed subfolders under docs/ship/<task-id>/ (input/, product/, design/, engineering/, quality/, delivery/, archive/). Prefer Markdown; use YAML/JSON only when a later agent or script consumes the structure.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

See the full security report

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

Popularity

Repository stars
93
Repository forks
8
7-day trend score
22

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/heliohq/ship/use-ship/badge)](https://verified-skill.com/skills/heliohq/ship/use-ship)

Something wrong with this skill or its page? Tell us.