ship

Automate the Git workflow from worktree to merged main branch.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bismuthdigital/claude-project-template --skill ship-bismuthdigital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/bismuthdigital/claude-project-template/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/bismuthdigital/claude-project-template --skill ship-bismuthdigital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, ruff, mypy, pytest, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire process of taking code changes from a development worktree, committing them, creating a pull request, merging it, and syncing the local repository, all in one command.

Core Features & Use Cases

  • End-to-End Workflow: Manages commits, version bumps, rebasing, PR creation, merging, and local syncing.
  • Worktree Integration: Designed for Git worktree workflows, ensuring safe and isolated development.
  • Use Case: After completing a feature in a worktree, you can run /ship to automatically handle all the steps needed to get that code merged into the main branch, including resolving conflicts and ensuring CI passes.

Quick Start

Run the ship skill to commit, version, rebase, push, create a PR, merge, and sync your changes.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a git worktree to main branch deployment workflow?

Automating a git worktree to main branch workflow involves staging, committing, rebasing, pushing, and merging pull requests. This skill handles the complete deployment process end-to-end, including pre-flight checks and CI parity verification.

What is the best way to resolve git rebase conflicts when merging a pull request?

Resolving git rebase conflicts during a pull request merge requires intelligent conflict resolution checks. This skill automates rebasing onto the latest main branch with robust error handling to ensure production-ready conflict resolution.

Does this merge automation support squash, merge, and rebase pull request strategies?

Yes, pull request merge automation supports configured squash, merge, and rebase strategies. You can configure the specific merge method to integrate worktree code changes into the main branch.

Can I run pytest, mypy, and ruff checks before pushing a pull request?

Yes, you can run pytest, mypy, and ruff checks before pushing. This skill performs robust pre-flight checks and CI parity verification to ensure code quality before creating and merging the pull request.

How do I sync my local repository after merging a pull request?

Syncing a local repository after merging a pull request involves pulling the latest changes from the remote main branch. This skill automates the local repository sync as the final step in the end-to-end shipping workflow.

Do I need the gh CLI to create pull requests from a git worktree?

Yes, you need the gh CLI dependency to create pull requests from a git worktree. The skill uses the GitHub CLI to automate PR creation with relevant details and configure the merge process.