ship

Automate code shipping with tests, version bumps, and PR creation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/him55710-sudo/uni-foli --skill ship-him55710-sudo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/him55710-sudo/uni-foli/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/him55710-sudo/uni-foli --skill ship-him55710-sudo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically ships code changes by orchestrating base-branch handling, tests, diff reviews, version bumps, CHANGELOG updates, commits, pushes, and PR creation to get changes into the main line safely.

Core Features & Use Cases

  • Auto-detect base branch and run tests to ensure changes are safe to merge.
  • Bump version, update CHANGELOG, commit, push, and open a PR on the target branch.
  • Proactively invoke the ship workflow when the user asks to deploy, push, or create a PR.
  • Works within standard Git workflows on GitHub and GitLab, with CI integration and review gates.

Quick Start

Say "/ship" when your code is ready and I will execute the full ship workflow from the current branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git pull request creation with version bumps and changelog updates?

You can automate PR creation by triggering a workflow that detects the base branch, runs tests, bumps the version, updates the CHANGELOG, commits, pushes, and opens a pull request on GitHub or GitLab automatically.

What is an automated release workflow for feature branches?

An automated release workflow for feature branches handles diff reviews, test execution, version bumps, and PR creation to get code changes into the main line safely. It wires together CI runs and review gates to ensure changes are ready for merge.

Does this automated PR workflow work with both GitHub and GitLab repositories?

Yes, the automated shipping workflow works within standard Git workflows on both GitHub and GitLab repositories. It handles feature branches, CI integration, and review gates across both platforms to ensure changes are safe to merge.

How do I handle test failures or conflicts during automated code shipping?

Handling test failures or conflicts during automated code shipping is managed per policy within the workflow. The process runs tests to ensure changes are safe to merge and proactively handles any conflicts that arise before opening the final PR.

Do I need a valid Git workspace with a remote to automate pushing code changes?

Yes, you need a valid Git workspace with a configured remote to automate pushing code changes. The workflow requires base-branch detection and remote access to execute tests, commit changes, push to the target branch, and create the PR.

When should I use an end-to-end automated shipping workflow for my commits?

You should use an end-to-end automated shipping workflow when your code changes are ready and you need to safely deploy, push, or create a PR. It ensures changes pass tests and review gates before merging into the main line.