ship

Automates merging, testing, versioning, and pull request creation for feature branches.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/dhnpmp-tech/project-agent --skill ship-dhnpmp-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/dhnpmp-tech/project-agent/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/dhnpmp-tech/project-agent --skill ship-dhnpmp-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves a repetitive chain of manual steps — merging the base branch, running tests, reviewing the diff, bumping the version, updating the changelog, committing, pushing, and opening a PR. This Skill runs that entire release workflow automatically as a single non-interactive command. ## Core Features & Use Cases - Automated Ship Pipeline: Detects the base branch, merges it into the feature branch, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates the PR. - Review Readiness Gate: Displays a dashboard of prior engineering, CEO, design, and adversarial reviews, with staleness detection against the current HEAD before allowing the ship to proceed. - Test Framework Bootstrap: Detects the project runtime (Node, Ruby, Python, Go, Rust, PHP, Elixir) and sets up a test framework with an example test if none exists. - Use Case: A developer finishes a feature branch and types "/ship" — the Skill merges main, runs the test suite, auto-generates the changelog from the diff, creates bisectable commits, and outputs the PR URL without further prompts. ## Quick Start Ask the AI to ship the current feature branch by running the ship workflow and creating a pull request.

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 from a feature branch?

Run the ship workflow from your feature branch. It detects the base branch, merges it in, runs tests, bumps the version, updates the changelog, commits, pushes, and creates the PR using the GitHub CLI, returning the PR URL at the end.

How does the ship workflow handle merge conflicts with the base branch?

Simple conflicts in files like VERSION or CHANGELOG are auto-resolved. Complex or ambiguous conflicts stop the workflow and display the conflicting files so you can resolve them manually before re-running.

Does the ship workflow require a code review before merging?

An engineering review within the last 7 days is required by default and shown in the Review Readiness Dashboard. You can override the gate per branch, or disable it globally with gstack-config set skip_eng_review true.

What happens if my project has no test framework configured?

The workflow detects your runtime (Node, Ruby, Python, Go, Rust, PHP, or Elixir), researches current best practices, and offers to install and configure a test framework with an example test. Declining writes a .gstack/no-test-bootstrap marker.

When does the ship workflow stop and ask for input?

It stops for unresolvable merge conflicts, in-branch test failures, MINOR or MAJOR version bumps, missing engineering review without override, and plan items marked not done. Everything else, including changelog content and commit messages, is fully automatic.