ship

Automate branching, PR creation, CI gate management, and local cleanup.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/xinye1/xl-skills --skill ship-xinye1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/xinye1/xl-skills/tree/main/skills/ship
Command: npx skills add https://github.com/xinye1/xl-skills --skill ship-xinye1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of the development lifecycle by automating the entire path from local code changes to a merged, cleaned-up pull request, ensuring no steps are missed.

Core Features & Use Cases

  • State-Aware Workflow: Automatically detects whether you are starting a new feature, iterating on an existing PR, or performing post-merge cleanup.
  • Independent Verification: Enforces mandatory local testing, linting, and independent code review before any merge occurs.
  • Use Case: When you have finished a set of changes and want to ship them, this skill handles the branching, committing, PR creation, CI gate management, and final branch cleanup in a single, cohesive flow.

Quick Start

Use the ship skill to push your current changes and manage the entire pull request and merge process for your active branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the git pull request lifecycle from local commit to merge?

You can automate the entire pull request lifecycle by using a state-aware workflow that handles branching, PR creation, CI gate management, and local branch cleanup in a single cohesive flow. This ensures consistent, verified, and independently reviewed code merges.

How does CI gate management work for automated pull requests?

CI gate management works by enforcing mandatory local testing, linting, and independent code review before any merge occurs. It integrates with repository-specific CI/CD configurations to verify that all checks pass successfully prior to merging.

Do I need the gh CLI to automate code shipping workflows?

Yes, you need the gh CLI along with git to automate code shipping workflows. These tools are required to manage branching, create pull requests, handle CI gate enforcement, and perform local cleanup after merging.

Can I use this automated shipping workflow to iterate on an existing pull request?

Yes, the automated shipping workflow is state-aware and automatically detects whether you are starting a new feature or iterating on an existing pull request. It adapts the end-to-end flow to manage updates and CI verification seamlessly.

What is the best way to ensure independent code review before merging local changes?

The best way to ensure independent code review is to enforce it as a mandatory step within an automated code shipping lifecycle. This approach requires independent verification, alongside local testing and linting, before allowing any branch to merge.

When should I avoid automating the end-to-end code shipping lifecycle?

You should avoid automating the end-to-end code shipping lifecycle if your software development workflow lacks consistent repository-specific CI/CD configurations or does not require independent code review and verified merges.