ck:ship

Automate software releases from feature branch to pull request with one command.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The ck:ship skill solves the problem of managing and automating the release process of software, including merging, testing, reviewing, committing, pushing, and creating pull requests, making it a one-command solution from feature branch to pull request URL.

Core Features & Use Cases

  • Unified Pipeline: Consolidates multiple steps like merging, testing, and committing into a single command.
  • Flexible Branching: Ships to main/master for official releases or dev/beta branches for beta releases.
  • Conditional Execution: Allows skipping tests, reviews, journaling, and documentation updates based on flags.
  • Token Efficiency: Delegates certain steps to subagents, runs background tasks, and optimizes API calls for token conservation.
  • Use Case: A developer wants to ship a new feature to the main branch. They use the ck:ship official command, which triggers all necessary steps without manual intervention.

Quick Start

Run the command ck:ship official from your feature branch to ship to the main branch with all checks.

Frequently Asked Questions about ck:ship

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

FAQPage Schema
How do I automate the software release process from a feature branch to a pull request?

You can automate the software release process using a single command that handles merging, testing, reviewing, committing, pushing, and creating a pull request. This provides a unified pipeline from feature branch to pull request URL.

What is the best way to streamline continuous integration and deployment for a new feature?

The best way to streamline continuous integration and deployment is using a one-command release automation tool. It triggers necessary CI/CD steps like testing and committing without manual intervention, optimizing API calls for token conservation.

Can I ship code to a beta branch instead of the main master branch?

Yes, you can ship to beta branches. The release automation supports flexible branching, allowing you to target dev or beta branches for beta releases, while using main or master branches for official releases.

How do I skip tests or documentation updates during a continuous integration push?

You skip tests or documentation updates during a continuous integration push by using conditional execution flags. The automation supports skipping specific steps like reviewing, journaling, and documentation updates based on your configuration.

Does release automation work across different software frameworks?

Yes, release automation works across various software frameworks. It is optimized for token efficiency by delegating certain steps to subagents and running background tasks, ensuring framework-agnostic compatibility.