shipping-code

Automate end-to-end ship workflows on GitHub feature branches to produce PRs.

1|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/allen-hsu/agent-arsenal --skill shipping-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipping-code
Source: https://github.com/allen-hsu/agent-arsenal/tree/main/plugins/shipping/skills/shipping-code
Command: npx skills add https://github.com/allen-hsu/agent-arsenal --skill shipping-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the end-to-end ship workflow for software projects, eliminating manual release steps and reducing risk during code deployment.

Core Features & Use Cases

  • Base-branch detection and merge into the feature branch for shipping
  • Automated test execution, diff analysis, and generation of bisectable commits
  • Auto-creates a PR with a comprehensive body and returns the PR URL for tracking
  • Non-interactive workflow that outputs the PR URL on success

Quick Start

Run the /ship command on a feature branch to execute the full pipeline and obtain the PR URL.

Frequently Asked Questions about shipping-code

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

FAQPage Schema
How do I automate a git workflow to create a pull request from a feature branch?

Automating a git workflow to create a pull request involves running a non-interactive ship process that detects the base branch, merges it, runs tests, and generates a ready-to-review PR with a comprehensive body.

What is a fully automated ship workflow for GitHub repositories?

A fully automated ship workflow is an end-to-end process that applies base-merge pre-flight checks, executes tests, analyzes diffs, and creates bisectable commits to output a ready-to-review PR URL.

Does the automated ship process require manual intervention during pull request generation?

The automated ship process does not require manual intervention during pull request generation, as it implements a deterministic, non-interactive workflow that automatically outputs the PR URL upon success.

How do pre-flight checks and diff analysis work in an automated CI ship process?

Pre-flight checks and diff analysis in an automated CI ship process work by detecting the base branch, merging it into the feature branch, analyzing the resulting code differences, and generating bisectable commits before pushing.

Can I use this automated ship workflow across multiple feature branches in GitHub?

You can use this automated ship workflow across multiple feature branches in GitHub repositories, as it applies deterministic base-branch detection, test execution, and PR generation to produce trackable pull request URLs.

Why should I use an automated workflow for shipping code instead of manual release steps?

Using an automated workflow for shipping code eliminates manual release steps and reduces deployment risk by ensuring deterministic test execution, diff analysis, and bisectable commit creation before PR generation.