ship

Automate merging, testing, versioning, changelog generation, and pull request creation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/XDCIndia/SkyNet --skill ship-xdcindia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/XDCIndia/SkyNet/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/XDCIndia/SkyNet --skill ship-xdcindia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of shipping changes: merging main, running tests, reviewing diffs, updating version numbers, generating changelogs, committing changes, pushing branches, and creating pull requests, eliminating manual handoffs and human delays.

Core Features & Use Cases

  • End-to-end automation of the ship cycle on feature branches or main, including conflict handling and automated PR creation.
  • Deterministic, non-interactive workflow that performs pre-flight checks, test runs, and changelog/version updates without prompts.
  • Suitable for teams that want faster, repeatable release cycles with auditable commits and traceable PRs.

Quick Start

Invoke the /ship workflow to automatically merge, test, review diffs, bump VERSION, update CHANGELOG, commit, push, and open a PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the ship workflow for pull requests?

Automating the ship workflow for pull requests involves merging feature branches, running tests, updating version numbers, generating changelogs, and creating PRs. This Skill executes the entire non-interactive ship process deterministically without manual handoffs.

What is a non-interactive ship workflow in software development?

A non-interactive ship workflow is a deterministic, automated release process that performs pre-flight checks, conflict resolution, and CI integration without human prompts. It ensures safe, auditable operations across multiple environments while eliminating manual delays.

How do I automatically update version numbers and generate changelogs before creating a PR?

To automatically update version numbers and generate changelogs before creating a PR, the automated ship workflow bumps the VERSION file, updates the CHANGELOG, commits changes, pushes branches, and opens a pull request in a single end-to-end cycle.

Does the automated ship workflow handle conflict resolution and pre-flight checks?

Yes, the automated ship workflow handles conflict resolution and pre-flight checks by merging changes from feature branches into main and executing tests. It enforces safe, auditable operations with CI integration before committing and pushing branches.

Can I use this automated ship process across multiple environments?

Yes, the automated ship process applies to software development pipelines requiring deterministic, non-interactive ship processes across multiple environments. It integrates with CI to ensure repeatable release cycles with auditable commits and traceable PRs.

What is the best way to eliminate manual handoffs in a release cycle?

The best way to eliminate manual handoffs in a release cycle is to use an end-to-end automated ship workflow that merges branches, runs tests, reviews diffs, updates versions, generates changelogs, and creates pull requests without interactive prompts.