skills.rest
Thanh-apero
Thanh-aperoCOMMUNITY
Explore all skills by this author →
GitHub

ck:ship

Merge feature branches to main or beta with automated tests and reviews.

1|1|Updated Jan 15, 2026
Search Tags:#branch management#continuous integration#pipeline automation#software release#deployment process
One-click install
npx skills add https://github.com/Thanh-apero/apero-kit-cli --skill ck-ship-thanh-apero
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/Thanh-apero/apero-kit-cli/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/Thanh-apero/apero-kit-cli --skill ck-ship-thanh-apero

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The CK:Ship Skill simplifies the complex software release process by providing a single command that merges branches, tests, reviews, commits, and pushes to ensure smooth deployment to either main/master or beta branches.

Core Features & Use Cases

  • Branch Management: Handles merging main, test, review, and commit stages with a single command.
  • Pipeline Automation: Automates tests, reviews, and other necessary steps, minimizing manual work.
  • Target Flexibility: Ships code to the appropriate branch (main/master for official releases, dev/beta for beta releases) based on user input or automatic branch detection.
  • Use Case: When developing a feature branch, this skill can be used to ensure all the necessary steps for deployment are taken care of with one command.

Quick Start

To release a feature to the main branch with documentation, use the command: /ck:ship official

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 feature branches to main?▼

You can automate the software release process using a single command to merge branches, run tests, review, commit, and push changes to your main or master branch. This handles the entire deployment pipeline automatically.

What is the best way to streamline branch management for beta releases?▼

Streamline branch management for beta releases by automatically detecting and routing feature branch changes to designated dev or beta branches. This ensures proper testing and review stages are completed before pushing code.

Can I ship code to both main and beta branches with a single command?▼

Yes, you can ship code to either main/master or dev/beta branches using a single command. The target branch is determined automatically or based on your specific input, like using an official release command.

Does pipeline automation handle testing and committing before pushing changes?▼

Yes, pipeline automation handles testing, reviewing, and committing before pushing changes. This ensures that all necessary validation steps are completed automatically, minimizing manual work during the deployment process.

Is this deployment process suitable for all software development projects?▼

Yes, this deployment process is suitable for all types of software development projects requiring an efficient release process. It adapts to projects needing automated merging, testing, and pushing to main or beta branches.

Related Skills

Explore More Software Engineering Skills→
Neuron-Mr-WhiteNeuron-Mr-White
56

worktree-merge

Merge worktree branches into the main branch with context gathering and conflict resolution.

Community
Intermediate
Kingdaddy007Kingdaddy007
2

DEVOPS & INFRASTRUCTURE

Govern infrastructure provisioning, CI/CD pipelines, monitoring, and disaster recovery.

Community
Advanced
InverterNetworkInverterNetwork

requesting-code-review

Automates pre-commit code verification through static security analysis, linting, and independent review.

Official
Advanced
sitharaj88sitharaj88
1

azure-devops-pipelines

Generate Azure DevOps YAML pipelines for CI/CD with deployment strategies.

Community
Advanced