ck:ship

Automate merge, test, review, and PR workflows from a feature branch.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-ship-edgehunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-ship-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ship pipeline automates merging, testing, reviewing, versioning, changelog creation, and PR publication from a feature branch, reducing manual handoffs and human error.

Core Features & Use Cases

  • Single-command pipeline that moves a feature branch through tests, reviews, version bumps, changelog entries, and PR creation
  • Supports official (main/master) and beta (dev/beta) release paths with auto-detection
  • Flexible control via flags to skip tests, review, journal, or docs; includes auto-detection of target branches
  • Generates a structured PR with linked issues and a clear release narrative

Quick Start

Run /ck:ship to execute the full pipeline from a feature branch.

Frequently Asked Questions about ck:ship

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

FAQPage Schema
How do I automate a GitHub release pipeline from a feature branch?

Automate a GitHub release pipeline by running a single command to merge, test, review, and publish a pull request from your feature branch. This orchestrates pre-flight checks, version bumps, and changelog generation automatically.

Can I skip tests or code review when shipping a pull request?

Yes, you can skip tests, review, journal, or docs generation using flexible control flags when shipping a pull request. This allows you to bypass specific pipeline stages while still automating the core merge and PR creation workflow.

How do I create a release PR with linked issues and a changelog?

Create a release PR with linked issues and a changelog by running the automated ship pipeline. It generates a structured pull request containing a clear release narrative, updated changelog entries, and automatically linked issue references.

Does CI-CD automation support both beta and official release paths?

CI-CD automation supports both official and beta release paths with auto-detection. It automatically targets main/master branches for official releases and dev/beta branches for beta releases, applying the appropriate version bump and workflow.

What is the best way to streamline version bumps and journal updates during a release?

The best way to streamline version bumps and journal updates is using a single-command release pipeline. It auto-detects target branches, applies version increments, generates changelog entries, and updates journal and documentation files automatically.