ship

Automate branch completion by committing, pushing, creating pull requests, and cleaning up.

3|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill ship-adamcaviness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/AdamCaviness/agentic-toolkit/tree/main/skills/ship
Command: npx skills add https://github.com/AdamCaviness/agentic-toolkit --skill ship-adamcaviness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complete branch handoffs by automating commit, push, PR creation/merge, synchronization with main, and cleanup, reducing manual steps and mistakes.

Core Features & Use Cases

  • Automates commit, push, and PR creation for feature branches.
  • Chooses merge strategy based on repository policy and performs cleanup after merge.
  • Ensures local main is synced and stale branches are removed to keep the repo tidy.

Quick Start

Use the ship skill on your feature branch to automatically commit, push, merge, and clean up after review.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate Git branch merging and pull request cleanup?

You can automate Git branch merging and pull request cleanup through a workflow that commits changes, pushes to origin, creates or updates pull requests, and removes stale local branches. It detects repository policies to select an appropriate merge strategy for safe merging.

What is the best way to finish a Git feature branch end to end?

The best way to finish a Git feature branch end to end is to automate the commit, push, pull request creation, merge, and cleanup phases. This ensures your local main branch is synced and stale branches are removed to keep the repository tidy.

Do I need the gh CLI to automate pull requests and branch merging?

Yes, you need the gh CLI and Git installed to automate pull requests and branch merging. The workflow requires these dependencies to push changes, interact with repository policies, and manage pull request creation or updates.

How does a workflow choose a merge strategy for different Git repositories?

A workflow chooses a merge strategy for different Git repositories by detecting repository policies and applying local policy caching to govern merge decisions. This allows it to select an appropriate and safe merging approach for each feature branch.

Can I sync local main and clean up stale branches automatically after a merge?

Yes, you can sync local main and clean up stale branches automatically after a merge. The workflow handles post-merge cleanup by synchronizing your local main branch and removing stale local branches to keep the repository tidy.