ck:ship

Merge a feature branch, run tests, and create a pull request.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-ship-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/ship
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-ship-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns a feature branch into a safely shipped pull request by coordinating merge checks, tests, review, versioning, changelog updates, and PR creation.

Core Features & Use Cases

  • End-to-end shipping workflow: Detects ship mode, merges the target branch, runs tests, performs review checks, bumps versions, updates changelogs, and pushes the result.
  • Release traceability: Finds or creates linked GitHub issues, then builds a structured PR body with summary, review notes, test results, and ship mode.
  • Use Case: A developer finishes a feature branch and wants one guided command that prepares the release, handles routine updates, and opens the PR without manual orchestration.

Quick Start

Use the ship skill to ship my current feature branch to the appropriate target branch and create the pull request.

Frequently Asked Questions about ck:ship

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

FAQPage Schema
How do I automate creating a pull request from a feature branch in one step?

You can automate pull request creation by using a guided command that merges the target branch, runs tests, performs review checks, bumps versions, and opens the PR. This coordinates the entire feature branch shipping workflow without manual orchestration.

What is the best way to prepare a feature branch for a GitHub release?

The best way to prepare a feature branch for a GitHub release is to run an end-to-end workflow that detects the ship mode, merges the target branch, validates code, updates changelogs, and links GitHub issues before pushing the result and opening the PR.

Do I need the GitHub CLI to automate branch merging and PR creation?

Yes, you need the GitHub CLI along with Git to automate branch merging and PR creation. The workflow relies on these tools to link issues, push validated branches, and generate structured PR bodies with review notes and test results.

How does branch-aware mode detection work for beta and official releases?

Branch-aware mode detection automatically identifies the target branch to determine the release type. It applies official releases to main or master branches and routes beta releases to dev or beta branches, ensuring the correct versioning and changelog updates are applied.

What happens if automated tests fail or merge conflicts occur during release automation?

When automated tests fail or merge conflicts occur during release automation, the workflow applies guarded handling to stop the process. This prevents broken code from being pushed and ensures critical review findings are resolved before the PR is created.

Can I link GitHub issues and update changelogs automatically when shipping code?

Yes, you can link GitHub issues and update changelogs automatically when shipping code. The workflow finds or creates linked issues and builds a structured PR body that includes the summary, review notes, test results, and ship mode.