ship

Automate pull request creation, merging, and branch promotion in GitHub repositories.

11|2|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/jswest/bartleby --skill ship-jswest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/jswest/bartleby/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/jswest/bartleby --skill ship-jswest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of shipping code changes, automating the creation of pull requests, and promoting merges for efficient software development workflows.

Core Features & Use Cases

  • Automated Pull Requests: Create pull requests from issue branches, with support for omnibus branches.
  • Promotion of Merges: Automatically promote finished omnibus branches to the main branch.
  • Configurable: Customize the workflow through a .toml configuration file.
  • Use Case: When working on a large feature branch with multiple sub-issues, use this Skill to automatically manage the branching, merging, and promotion process, ensuring a smooth integration with minimal manual intervention.

Quick Start

Run /ship #<issue> to ship a code change associated with the specified issue number.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate pull requests and branch promotion in GitHub repositories?

You can automate pull requests and branch promotion by running a command like `/ship #<issue>` against a GitHub repository. The Skill automatically creates pull requests from issue branches, merges code, and promotes finished omnibus branches to the main branch.

What do I need to set up before automating code shipping for GitHub issues?

Before automating code shipping, you need a GitHub repository with an active issue tracker and a `.claude/ship.toml` configuration file in your project. This configuration file allows you to customize the workflow with flags for planning, testing, and model tiering.

How does merging code from multiple sub-issues into a feature branch work?

Merging code from multiple sub-issues is handled through omnibus branches. The Skill manages the branching, merging, and promotion process for these omnibus branches, ensuring smooth integration of large feature branches with minimal manual intervention.

Can I customize the code shipping workflow for planning and testing?

Yes, you can customize the code shipping workflow through the `.claude/ship.toml` configuration file. This file supports configurable flags specifically for planning, testing, and model tiering to adapt the automation to your development process.

What is the best way to ship code changes associated with a specific issue number?

The best way to ship code changes for a specific issue is to run `/ship #<issue>` with the target issue number. This directly automates the creation of pull requests and handles both leaf issues and omnibus branches for the specified issue.