skills.rest
TNHoang2708
TNHoang2708COMMUNITY
Explore all skills by this author →
GitHub

ck:ship

Automate GitHub release workflows from feature branches to pull requests.

1|Updated Jun 16, 2026
Search Tags:#version control#github#release automation#continuous integration#pull request management
One-click install
npx skills add https://github.com/TNHoang2708/Gym_Ver2 --skill ck-ship-tnhoang2708
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:ship
Source: https://github.com/TNHoang2708/Gym_Ver2/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/TNHoang2708/Gym_Ver2 --skill ck-ship-tnhoang2708

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the entire release process from feature branch to pull request, automating tasks like merging, testing, and documentation updates to streamline the release workflow.

Core Features & Use Cases

  • Unified Pipeline: Automates the steps from merging to pushing, creating pull requests, and updating documentation.
  • Conditional Steps: Supports options to skip tests, reviews, journal entries, and documentation updates.
  • Mode Detection: Automatically determines if a release is for 'official' or 'beta' branches based on branch naming conventions.
  • Integration with GitHub: Uses GitHub API to link issues, create pull requests, and perform other GitHub operations.
  • Use Case: Streamline the release of new features or beta updates by running a single command from a feature branch.

Quick Start

Run the /ck:ship command on your feature branch to initiate the release process.

Frequently Asked Questions about ck:ship

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

FAQPage Schema
How do I automate pull request creation from a feature branch?▼

Release automation handles merging, testing, and documentation updates by executing a single command from your feature branch, using GitHub branch naming conventions to detect official or beta release modes.

How does branch naming affect release automation for GitHub pull requests?▼

Branch naming affects release automation by enabling automatic mode detection. The system determines if a release targets an official or beta branch based on the naming conventions used, adjusting the workflow accordingly.

Can I skip tests and documentation updates during continuous integration?▼

Yes, you can skip tests, reviews, journal entries, and documentation updates during continuous integration. The release pipeline supports conditional steps, allowing you to toggle these optional processes on or off.

Does GitHub release automation link issues automatically when creating pull requests?▼

Yes, GitHub release automation links issues automatically when creating pull requests. It integrates directly with the GitHub API to perform pull request creation and issue linking as part of the unified pipeline.

What is the best way to streamline beta updates through a continuous integration pipeline?▼

The best way to streamline beta updates is using an automated release pipeline that detects beta branch naming, merges changes, and creates a pull request via the GitHub API, all from a single command.

Related Skills

Explore More Software Engineering Skills→
vanducngvanducng
5

ship

Automate feature branch landing into main or beta with testing and PR creation.

Community
Advanced
liujiayi3703liujiayi3703

babysit

Monitor pull request status and manage review threads via GitHub CLI.

Community
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
ToqsickToqsick

github-grayhack-workflow

Automate GitHub issue creation, branch management, pull requests, and documentation updates.

Community
Advanced