ship-it

Push the current branch to GitHub and open a pull request.

Updated May 14, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/vector --skill ship-it-leroyadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-it
Source: https://github.com/LeroyAdonis/vector/tree/main/.agents/skills/ship-it
Command: npx skills add https://github.com/LeroyAdonis/vector --skill ship-it-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Push the current branch to a remote GitHub repository and open a pull request, reducing manual steps and context switching for shipping code.

Core Features & Use Cases

  • Automates GitHub PR workflow: detects unpushed commits, creates a feature branch when needed, pushes to origin, and opens a PR to accelerate collaboration.
  • Handles prerequisites and guardrails: verifies Git, gh CLI installation, authentication, and a configured remote to prevent failed shipping.
  • Supports typical developer workflows: works for feature branches, default-branch pushes, and avoids duplicating PRs by checking for existing ones.

Quick Start

Run /ship-it to push your current branch and open a pull request.

Frequently Asked Questions about ship-it

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

FAQPage Schema
How do I automatically push a git branch and create a pull request?

To automatically push a git branch and create a pull request, this Skill coordinates environment checks, pushes unpushed commits to origin, and opens a PR. It verifies prerequisites like gh CLI authentication and a configured remote to streamline the process.

Do I need gh CLI authentication to automate opening a GitHub pull request?

Yes, gh CLI authentication is required to automate opening a GitHub pull request. The Skill verifies Git and gh CLI installation, confirms your authentication status, and checks for a configured remote repository to prevent failed shipping.

What happens if I run a pull request automation while on the default branch?

When running pull request automation on the default branch, the Skill generates a new feature branch before pushing changes. It handles branching decisions automatically and ensures no duplicate PRs are created by checking for existing open pull requests.

How does git branch automation handle uncommitted changes?

Git branch automation handles uncommitted changes by enforcing checkpoint usage. This ensures your local modifications are safely committed before the Skill pushes the current branch to the remote GitHub repository and initiates pull request creation.

Can I avoid creating duplicate pull requests when pushing unpushed commits?

Yes, you can avoid creating duplicate pull requests when pushing unpushed commits. The Skill checks for existing open PRs on your current branch before attempting to create a new one, preventing redundant review requests.

What are the limitations of automating GitHub PR workflows from the command line?

Limitations of automating GitHub PR workflows include requiring a configured remote repository and valid gh CLI authentication. The automation also enforces checkpoint usage for uncommitted changes, meaning you cannot skip local commit steps before shipping code.