shipit

Automate pull request merging with git and GitHub CLI commands.

8|1|Updated Mar 28, 2026

Search Tags:#automation #git #pull request #github #merge #ci

Ready to run

npx skills add https://github.com/bostonaholic/team --skill shipit-bostonaholic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shipit
Source: https://github.com/bostonaholic/team/tree/main/skills/shipit
Command: npx skills add https://github.com/bostonaholic/team --skill shipit-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, error-prone process of merging pull requests by automating the verification of CI status, branch synchronization, and squash-merge execution.

Core Features & Use Cases

Automated CI Verification: Ensures all required checks pass before merging, with built-in timeout protection.
Safe Synchronization: Automatically rebases the branch if it has fallen behind the base and uses force-with-lease to prevent accidental data loss.
Standardized Merging: Performs squash-merges to maintain a clean, linear project history while preserving PR metadata.

Quick Start

Invoke the shipit skill to automatically push local commits, verify CI status, and squash-merge the current branch into the base branch.

Frequently Asked Questions about shipit

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

FAQPage Schema

How do I automate merging a pull request only after CI checks pass?▼

Automating a pull request merge with CI gating requires coordinating git operations and GitHub CLI commands to verify CI status and execute a squash-merge. This skill automates that end-to-end lifecycle, ensuring all required checks pass before merging the pull request.

What is the safest way to rebase a git branch that has fallen behind the base branch?▼

Safely rebasing a branch that has fallen behind involves using force-with-lease to prevent accidental data loss. This skill automatically rebases the branch and applies force-with-lease synchronization to maintain branch protection without overwriting remote changes.

How do I maintain a linear commit history when merging pull requests?▼

Maintaining a linear commit history is achieved by performing squash-merges that consolidate branch commits into a single commit. This skill standardizes the merging process by executing squash-merges to preserve pull request metadata while keeping the project history clean and linear.

Do I need the GitHub CLI installed to automate pull request merges?▼

Yes, you need the GitHub CLI (gh) and git installed and authenticated in your environment to automate pull request merges. This skill relies on these dependencies to coordinate git operations, verify CI status, and execute the merge commands.

Can I automate pushing local commits and merging a branch in one step?▼

Yes, you can automate pushing local commits and merging a branch in a single invocation. This skill automatically pushes local commits, verifies the required CI status, and squash-merges the current branch into the base branch.

What happens if CI checks time out during an automated pull request merge?▼

If CI checks time out during an automated pull request merge, the process includes built-in timeout protection to halt the merge. This ensures the branch is not merged until all required CI checks explicitly pass within the protected timeframe.