ck:ship

Automate the software release pipeline from feature branch to pull request.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-ship-auxi-wardrobe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/auxi-wardrobe/auxi-all-in/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-ship-auxi-wardrobe

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the entire release pipeline from feature branch to pull request URL, automating steps such as merging, testing, reviewing, committing, and pushing. Simplifies the shipping process for both official and beta releases.

Core Features & Use Cases

  • Unified Command: Ship feature branches with a single command, covering merging, testing, and pushing.
  • Automated Testing: Runs tests to ensure code quality.
  • Version Control: Bumps version numbers and commits changes.
  • Documentation: Generates documentation and journal entries for release notes.
  • Use Case: Save time and reduce errors in your release process by automating it with this skill.

Quick Start

Run the ck:ship command on your feature branch to begin the shipping process.

Frequently Asked Questions about ck:ship

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

FAQPage Schema
How do I automate merging, testing, and version bumping for a GitHub release?

Automated release pipelines handle merging, testing, reviewing, and version bumping through a single command. They run automated tests to ensure code quality, then commit and push changes to generate a pull request URL for the release.

Do I need the GitHub CLI to automate PR creation in my release pipeline?

Yes, the GitHub CLI is required to automate pull request operations in your release pipeline. The release automation process requires the GitHub CLI specifically to handle merging, reviewing, and creating pull request URLs within your project's repository.

What is the best way to streamline software releases from a feature branch to a pull request?

The best way to streamline software releases is using a unified command that automates the entire pipeline from feature branch to pull request. This approach manages merging, testing, reviewing, committing, and pushing to simplify both official and beta releases.

Can I use this release automation tool for both official and beta releases?

Yes, you can use this release automation tool for both official and beta releases. It simplifies the shipping process by managing the entire release pipeline, including version control, automated testing, and documentation generation for release notes.

What dependencies are required to set up automated version control and release management?

To set up automated version control and release management, you need git, the GitHub CLI (gh), and semver as dependencies. These tools enable the automation of merging, testing, version bumping, and pull request creation within your GitHub repository.