heliohq

heliohq/ship

Plugin Claude Code

Helio plugin registry.

heliohq/ship

Plugin Claude Code

An agent-routed harness for end-to-end software product development.

heliohq/ship

MCP server Claude CodeCodexCursor +2

MCP server "codex" as configured in heliohq/ship. Launched with codex mcp-server.

heliohq/ship

Instructions file CodexOpenCode

Instructions for heliohq/ship, covering agents.md, commands, repository map, architecture and code style.

heliohq/ship

Hook

Runs when a session starts on startup, clear and compact, executing session-start.sh via bash. From heliohq/ship.

heliohq/ship

Hook

Runs before the agent uses a tool, executing phase-guardrail.sh via bash. From heliohq/ship.

heliohq/ship

Hook

Runs when the agent finishes a response, executing stop-gate.sh via bash. From heliohq/ship.

heliohq/ship

Skill Claude CodeCodex

System-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries"…

heliohq/ship

Skill Claude CodeCodex

Run Ship's full production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, and handoff. Use only for explicit /ship:auto, auto pipeline requests, or end-to-end delivery.

heliohq/ship

Skill Claude CodeCodex

Plan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto.

heliohq/ship

Skill Claude CodeCodex

Implement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for "implement", "build/code this plan", or targeted fix findings. If no plan exists, use /ship:design first.

heliohq/ship

Skill Claude CodeCodex

Add durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA.

heliohq/ship

Skill Claude CodeCodex

Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.

heliohq/ship

Skill Claude CodeCodex

Runtime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review.

heliohq/ship

Skill Claude CodeCodex

Improve existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR.

heliohq/ship

Skill Claude CodeCodex

Static code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with file:line evidence. Use for code review or bug checks. Not runtime QA.

heliohq/ship

Skill Claude CodeCodex

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.

heliohq/ship

Skill Claude CodeCodex

Create or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself…