Ship

Name: Ship
Availability: InStock
Author: phuaky

Automate end-to-end release workflows from feature branches through publishing and verification.

2|Updated Mar 5, 2026

Search Tags:#git #versioning #deployment #ship #ci #cd

Ready to run

npx skills add https://github.com/phuaky/pai-skills --skill ship-phuaky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Ship
Source: https://github.com/phuaky/pai-skills/tree/main/skills/Ship
Command: npx skills add https://github.com/phuaky/pai-skills --skill ship-phuaky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automating the end-to-end release process for feature branches to reduce manual handoffs, ensure repeatable deployments, and accelerate delivery.

Core Features & Use Cases

Automated validation, integration, versioning, and publishing of code changes
PR creation, changelog updates, and deployment health checks as part of a single workflow
Rollback support and configurable per-project settings to adapt the pipeline to different projects
Use Case: A feature branch goes through validation, lands on main via PR, and releases with an updated changelog in one command.

Quick Start

Trigger the Ship workflow on a feature branch to automatically validate, integrate, version, publish, and verify deployment.

Frequently Asked Questions about Ship

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

FAQPage Schema

How do I automate end-to-end release workflows from feature branches to deployment?▼

Automating end-to-end release workflows handles validation, integration, versioning, publishing, and post-deploy verification. Triggering the workflow on a feature branch automatically lands code via PR and updates the changelog in one command.

Can I run deployment health checks and rollbacks within an automated CI pipeline?▼

Deployment health checks and rollbacks are supported within the automated pipeline. You can configure optional post-deploy health verification and trigger rollback procedures directly if deployment validation fails.

Do I need a specific configuration file to set up project-specific release automation?▼

Project-specific release automation requires a per-project .ship.json configuration file. This file defines customizable base settings, allowing the pipeline to adapt validation, versioning, and deployment steps to different projects.

How does versioning and changelog updating work when merging a feature branch?▼

Versioning and changelog updating happen automatically during feature branch integration. The workflow creates a PR, updates the changelog, applies versioning, and publishes the code changes once validation passes.

Can I test deployment automation without pushing changes to production?▼

You can test deployment automation without pushing to production using dry-run mode. The pipeline supports pre and post hooks alongside dry-run execution to validate the end-to-end workflow safely before applying changes.