ship

Coordinate merged code delivery through CI/CD pipelines and production readiness checks.

3|Updated Jan 27, 2026

Search Tags:#automation #ci/cd #deployment #verification #release-management #ship

Ready to run

npx skills add https://github.com/open-horizon-labs/skills --skill ship-open-horizon-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/open-horizon-labs/skills/tree/main/ship
Command: npx skills add https://github.com/open-horizon-labs/skills --skill ship-open-horizon-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship is the final step of the Execution phase. Code that isn't in users' hands isn't delivering value. This skill identifies and removes friction in your delivery path.

Core Features & Use Cases

Identify and optimize the delivery path from code to running systems.
Assess delivery-path friction across review, merge, gate, and deploy stages.
Coordinate shipping actions and post-deploy verification with guardrails.
Example: trigger CI/CD pipelines, coordinate approvals, and verify production readiness.

Quick Start

Ship the merged code to the target environment and verify the deployment is healthy.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I coordinate end-to-end code deployment from staging to production?▼

Code deployment coordination maps the delivery path from merged code to running systems, triggering CI/CD pipelines and coordinating approvals to ensure reliable production releases.

What's the best way to identify and remove friction in a CI/CD delivery path?▼

Friction in a CI/CD delivery path is identified by assessing review, merge, gate, and deploy stages, measuring their respective times to isolate and remove bottlenecks slowing down releases.

How do I verify production readiness and post-deploy health after a release?▼

Production readiness verification executes deployment actions and validates post-deploy health using built-in guardrails, triggering an automatic rollback if deployment health checks fail.

Can I trigger CI/CD pipelines and coordinate approvals for different environments?▼

Yes, triggering CI/CD pipelines and coordinating approvals across staging and production environments is supported, applying guardrails to validate readiness before executing deployment actions.

When do I need to measure review, merge, and gate times for release management?▼

Measuring review, merge, and gate times is needed when optimizing release management to assess delivery-path friction, ensuring merged code reaches user environments with maximum velocity.

What happens if post-deploy verification fails during a production release?▼

If post-deploy verification fails during production release, rollback guardrails activate to revert the deployment, ensuring system reliability and preventing unhealthy code from affecting users.