ship-it

Automate Git workflows from branch creation to pull request merge.

Updated Jan 27, 2026

Search Tags:#automation #git #commit #branch #ship #pull-request

Ready to run

npx skills add https://github.com/alistairhendersoninfo/ninja_toolbox --skill ship-it-alistairhendersoninfo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/alistairhendersoninfo/ninja_toolbox/tree/main/.claude/skills/ship-it
Command: npx skills add https://github.com/alistairhendersoninfo/ninja_toolbox --skill ship-it-alistairhendersoninfo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ship-It automates the end-to-end lifecycle of code changes from branch creation through PR merge, reducing manual steps and errors in typical Git workflows.

Core Features & Use Cases

End-to-end shipping: sync main, create a feature branch, commit all changes, push, and merge via a pull request.
Automated PR scaffolding: generates PR bodies and handles co-author lines, with optional prompts when required information is missing.
Use Case: When shipping multiple commits in a single PR, or when onboarding new developers to a consistent merge process.

Quick Start

Execute the ship-it command with a branch name and commit message to automatically sync main, create a branch, commit and push changes, open a PR, and merge.

Frequently Asked Questions about ship-it

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

FAQPage Schema

How do I automate git commit, push, and pull request merge in one step?▼

You can automate end-to-end git shipping by running a script that syncs main, creates a feature branch, commits all changes, pushes, opens a pull request, and merges. This eliminates manual git commands across the entire PR lifecycle.

What is the best way to create a feature branch and merge it automatically?▼

The best way to create a feature branch and merge automatically is using a dedicated shipping script. It handles branch creation, commits all changes with git add -A, pushes to remote, and merges the pull request without manual intervention.

Do I need a local Git environment to automate pull request creation and merging?▼

Yes, you need a local Git environment to automate pull request creation and merging. The automation relies on a shell script at .claude/scripts/ship-it.sh to execute local git commands for branch creation, committing, pushing, and PR merging.

How does automated PR scaffolding handle missing commit messages or co-author lines?▼

Automated PR scaffolding handles missing information by issuing optional prompts during the shipping process. When commit messages or co-author lines are absent, the script pauses to request the required input before generating the PR body and merging.

Can I ship multiple commits in a single pull request using branch automation?▼

Yes, you can ship multiple commits in a single pull request using branch automation. The script commits all staged changes via git add -A and bundles them into one PR before merging, ensuring consistent grouping of related changes.

Why does my git branch automation fail before the PR merge step?▼

Git branch automation may fail before PR merge if the local repository is not synced with main or if required information like branch names is missing. The script attempts to sync main first and prompts for missing data to prevent merge failures.