ship

Name: ship
Availability: InStock
Author: fray-cloud

Automate code shipping from feature branches to production-ready pull requests.

Updated Mar 23, 2026

Search Tags:#automation #git #workflow #changelog #pr #ship #version-bump

Ready to run

npx skills add https://github.com/fray-cloud/coin --skill ship-fray-cloud

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/fray-cloud/coin/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/fray-cloud/coin --skill ship-fray-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automated, end-to-end release workflows from pre-flight checks to PR creation, reducing manual handoffs and mistakes.

Core Features & Use Cases

Pre-flight checks on the current branch and abort if on the base branch.
Automatic diff logging, test execution coordination, version bumps, changelog updates, and PR creation.
Non-interactive operation suitable for CI-like automation and bot-driven shipping.

Quick Start

Run the ship workflow in your repo to automatically ship changes by creating a PR against the base branch.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate git workflow shipping from feature branches to production-ready PRs?▼

Automate git workflow shipping by detecting the base branch, running pre-flight validation, updating changelogs, bumping versions, and creating PRs automatically. This non-interactive operation handles end-to-end shipping from feature branches without manual prompts.

Can I create pull requests and update changelogs automatically in a CI-like automation pipeline?▼

Yes, you can create pull requests and update changelogs automatically in CI-like automation. The non-interactive operation coordinates test execution, version bumps, and PR tooling integration without requiring manual prompts during the workflow.

What is the best way to handle version bumps and diff logging before opening a PR?▼

Handle version bumps and diff logging by automating pre-flight checks on the current branch. The workflow aborts if on the base branch, then coordinates test execution, generates diff logs, updates changelogs, and opens the PR automatically.

Does automated shipping support base-branch detection and conflict handling for non-interactive bot-driven releases?▼

Automated shipping supports base-branch detection and conflict handling for non-interactive bot-driven releases. The workflow detects the base branch automatically, validates the current branch, and manages conflict handling during automated PR creation.

Why does automated PR creation abort when I run the workflow directly on the base branch?▼

Automated PR creation aborts on the base branch as a pre-flight safety check. The workflow requires changes on a feature branch to ensure proper diff logging, version bumping, and changelog updates before creating a PR against the base branch.

What are the limitations of non-interactive automated shipping workflows for version bumps and changelog updates?▼

Non-interactive automated shipping workflows require a feature branch and will abort on the base branch. They depend on existing PR tooling integration for automated creation and rely on successful pre-flight validation and test execution before completing version bumps.