ship

Merge a feature branch, run tests, bump VERSION, update CHANGELOG, and create a pull request.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end "ship" workflow so engineers stop doing repetitive, error-prone steps when preparing a change for merge and release. It reduces manual friction around merging the base branch, running tests, bumping versions, updating changelogs, committing, and creating a PR.

Core Features & Use Cases

  • Auto-merge and sync: Fetches and merges the detected base branch into the feature branch before tests run.
  • Test-run and gating: Runs the test suite and enforces configurable gates, surfacing failures and triaging pre-existing issues.
  • Release hygiene: Bumps VERSION (auto-pick micro/patch), updates CHANGELOG from the diff, commits changes, and pushes.
  • PR creation: Creates a pull request with a generated body, includes review readiness info, and reports the PR URL on completion.
  • Use Case: Run when your feature is ready to land and you want a fully automated, reproducible sequence that merges, verifies, and opens a PR without manual commits.

Quick Start

Use the ship skill to merge the base branch into your feature branch, run tests, update version and changelog, commit and push, and open 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 merging a feature branch and creating a pull request?

Automating pull request creation involves fetching the base branch, running tests, bumping the version, updating the changelog, and pushing the commit before opening the PR.

How do I automatically update version and changelog files before opening a PR?

To automatically update version and changelog files before opening a PR, the workflow bumps the VERSION file by picking a patch increment and generates CHANGELOG entries from the branch diff before committing and pushing.

Can CI tests gate a pull request from being created if failures occur?

CI tests can gate pull request creation by enforcing configurable test rules; the workflow surfaces failures, triages pre-existing issues, and prevents PR creation if the gating rules are not satisfied.

What happens when merge conflicts occur while syncing the base branch?

When merge conflicts occur while syncing the base branch, the automated workflow applies fetch and merge operations and handles the conflicts directly before proceeding to test execution and release metadata updates.

Is there a way to generate PR review readiness info automatically?

Generating PR review readiness info automatically is handled during PR creation; the workflow creates a pull request with a generated body that includes the review readiness status and reports the PR URL upon completion.

Do I need to manually fix test failures before automating a merge and PR?

You do not need to manually fix all test failures before automating a merge; the workflow runs the test suite, applies auto-fixes where possible, and triages remaining failures against pre-existing issues before proceeding.