ship

Automates end-to-end release workflows from feature branch to main.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill ship-xza85hrf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Xza85hrf/claude-code-agent-kit/tree/main/.claude/skills/quality/ship
Command: npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill ship-xza85hrf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Ship automates the end-to-end release workflow from a feature branch to main, combining validation, testing, changelog generation, and PR creation to reduce manual toil and risk.

Core Features & Use Cases

  • Pre-flight checks ensure a release-ready branch before shipping
  • Automated test discovery and execution with clear rollback options
  • Changelog generation and rich PR bodies that include test results
  • Support for draft PRs and non-interactive modes for CI/CD pipelines

Quick Start

Run the ship skill to orchestrate a full release from your feature branch to main.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git release workflows from a feature branch to a pull request?

Automating git release workflows from a feature branch to a pull request is done by running pre-flight checks, executing tests, generating a changelog, and publishing a PR to main automatically.

Can I create draft PRs and skip tests for non-interactive CI pipelines?

Yes, you can create draft PRs and skip tests for non-interactive CI pipelines by applying optional automation flags during the release workflow orchestration.

Do I need git and gh installed to automate changelog generation and PR creation?

Yes, you need both git and gh installed because the release workflow relies on these dependencies to manage branch operations, generate changelogs, and publish pull requests.

What is the best way to ensure a feature branch is release-ready before merging to main?

The best way to ensure a feature branch is release-ready before merging to main is running automated pre-flight checks and test discovery to validate the branch state before publishing.

How does rollback work if automated tests fail during the release workflow?

If automated tests fail during the release workflow, rollback capabilities are provided in the final summary to safely revert the branch state and prevent broken code from publishing.