ship

Automates a test, build, review, deploy, and notify pipeline via opencode agents.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill ship-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/gstack-ship
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill ship-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually running tests, builds, code reviews, and deployments before shipping code is repetitive and error-prone. This Skill orchestrates the entire release pipeline as a single configurable workflow, delegating each stage to specialized agents and stopping automatically on failures. ## Core Features & Use Cases - Multi-Stage Pipeline: Runs test, build, review, deploy, and notify stages in sequence, each delegated to a dedicated agent (test-engineer, devops-specialist, reviewer). - Configurable via JSONC: Customize stages, agents, timeouts, failure behavior, deploy targets, and notification channels through .opencode/ship.jsonc. - Failure Handling & Retry: Stops the pipeline on stage failure when failOnFailure is set and supports resuming from the failed stage with --stage. - Use Case: After finishing a feature branch, run /ship --target production to execute the full test suite, typecheck and lint, a 4-layer code review, deployment to Vercel, and a desktop notification with the result summary. ## Quick Start Ask the agent to ship the current branch by running the ship pipeline with the default configuration.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run only specific stages of the ship pipeline?

Use the --stage flag to run selected stages, such as /ship --stage test or /ship --stage test,build. This lets you retry from a failure point or skip stages you do not need without editing the config file.

How do I configure the ship pipeline stages and agents?

Create a ship.jsonc file in your project's .opencode directory or the global opencode config directory. It defines the stages array plus per-stage settings like agent, commands, failOnFailure, timeout, deploy targets, and notification channels.

Can I deploy to production with the ship pipeline?

Yes, pass --target production to override the default preview target. The deploy stage uses the environments config to determine URL and alias behavior, and the pipeline stops for explicit user decision points like deploy target selection.

What happens when a pipeline stage fails?

If the failing stage has failOnFailure set to true, the pipeline stops immediately and reports the error details. You can resume from that point using /ship --stage with the failed stage name after fixing the issue.

Does the ship pipeline support a dry run mode?

Yes, the --dry-run flag shows what would execute without running any stage. This is useful for verifying your ship.jsonc configuration and stage ordering before triggering real tests, builds, or deployments.