ship

Automate the ship workflow from branch detection to pull request creation.

Updated Mar 31, 2026

Search Tags:#automation #git #workflow #testing #ship #pull-request

Ready to run

npx skills add https://github.com/huichen/gstack --skill ship-huichen

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship skill automatically coordinates the end-to-end process of releasing code by detecting the base branch, running tests, reviewing changes, bumping version numbers, updating CHANGELOGs, committing, pushing, and creating a pull request.

Core Features & Use Cases

Automates the full ship workflow from feature branch to PR, with deterministic steps and guardrails around tests, reviews, and versioning.
Ensures release notes and changelog updates are included in PR commits and metadata.
Handles edge cases like merge conflicts and multi-branch scenarios, returning the final PR URL for easy follow-up.

Quick Start

Run the ship workflow on a feature branch to automatically produce and open a PR once checks pass.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate creating a pull request with changelog and version bump?▼

Automating pull request creation with changelog and version bump requires running a deterministic ship workflow that executes tests, reviews diffs, updates release notes, and pushes commits to generate a PR URL.

What is the best way to run tests before opening a pull request automatically?▼

Running tests before opening a pull request automatically is handled by enforcing guardrails within an end-to-end ship workflow that validates checks, bumps versions, updates the changelog, and creates the PR upon success.

Does the automated ship workflow handle merge conflicts when generating a pull request?▼

The automated ship workflow handles merge conflicts by enforcing deterministic steps during the end-to-end process of reviewing diffs, bumping versions, updating changelogs, and generating a pull request.

How do I update the changelog and commit changes before pushing to a feature branch?▼

Updating the changelog and committing changes before pushing to a feature branch is achieved by running an automated ship workflow that detects the base branch, reviews diffs, modifies release notes, and commits the changes.

Can I automatically detect the base branch when preparing code for deployment?▼

Automatically detecting the base branch when preparing code for deployment is a core step of the ship workflow, which coordinates running tests, version bumping, changelog updates, and pull request creation.

Why do I need an automated workflow for end-to-end pull request generation?▼

An automated workflow for end-to-end pull request generation ensures deterministic release steps, includes proper test validation and release notes, handles edge cases like merge conflicts, and returns the PR URL for follow-up.