ck:ship

Automate GitHub release processes including merging, testing, and PR creation.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-ship-duy-tung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/duy-tung/claude-code-setup/tree/main/claude/skills/ship
Command: npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-ship-duy-tung

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the release process by automating tasks such as merging, testing, reviewing, and pushing code to GitHub.

Core Features & Use Cases

  • Automated Release Pipeline: Handles merge, test, review, commit, push, and PR creation.
  • Branch Detection: Automatically determines the target branch for official or beta releases.
  • Customizable Steps: Skippable steps for tests, reviews, journals, and documentation updates.
  • Use Case: Ship a feature branch to main/master or dev/beta with a single command, saving time and reducing errors.

Quick Start

Run the command /ck:ship to start the release process for your 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 my GitHub release workflow from testing to PR creation?

Automating your GitHub release workflow handles merging, testing, code review, version bumping, changelog generation, and PR creation in a single command. You can ship a feature branch to main or beta branches while skipping specific steps like documentation updates as needed.

Can I skip code review or testing steps during an automated GitHub merge?

Yes, you can skip steps like tests, code reviews, journals, or documentation updates during an automated GitHub merge. The release pipeline provides customizable steps, allowing you to bypass specific phases while still executing core branch detection and push operations.

Do I need the GitHub CLI installed to automate repository releases?

Yes, you need the GitHub CLI installed to automate repository releases. This dependency is required for the tool to handle merging, pushing code, and creating pull requests directly through your GitHub repositories.

What is the best way to handle version bumping and changelog generation before a push?

Handling version bumping and changelog generation before a push is executed automatically during the release pipeline. The process determines the target branch for official or beta releases and updates your documentation concurrently to streamline deployment.

Does this release automation tool work with different programming languages on GitHub?

Yes, this release automation tool works with different programming languages on GitHub. It automates the release process for code repositories across various language ecosystems, handling branch detection and PR creation uniformly.

How does branch detection work for beta versus official releases?

Branch detection for beta versus official releases works by automatically determining the target branch based on your repository structure. The automation routes your feature branch merges to main/master for official releases or dev/beta branches for pre-release deployments.