tkm:ship

Automate GitHub release steps for feature branches with conditional flags.

Updated May 13, 2026

Search Tags:#version control #CI/CD #GitHub #release automation #feature branch

Ready to run

npx skills add https://github.com/khapn-2933/agentic-coding-hands-on --skill tkm-ship

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tkm:ship
Source: https://github.com/khapn-2933/agentic-coding-hands-on/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/khapn-2933/agentic-coding-hands-on --skill tkm-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the release process by automating the steps of merging, testing, reviewing, committing, pushing, and opening pull requests for a feature branch.

Core Features & Use Cases

Automated Release Workflow: Execute a series of steps to prepare a feature branch for merging into the main branch.
Conditional Execution: Skip specific steps like tests, review, journaling, and documentation updates based on flags.
Version Control Integration: Seamlessly integrates with version control systems to manage branches and commits.
Use Case: When you have a feature branch ready to be merged, use this Skill to ensure all necessary checks are completed before the merge.

Quick Start

Run the command /tkm:ship to initiate the release process for your feature branch.

Frequently Asked Questions about tkm:ship

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

FAQPage Schema

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

You can automate this release process by orchestrating merge, test, review, commit, push, and pull request creation into a single command. This workflow requires the GitHub CLI to manage branch operations and open pull requests automatically.

Can I skip tests when automating a feature branch release?▼

Yes, you can skip tests during feature branch release automation by using specific conditional execution flags. These flags also allow you to bypass review, journaling, and documentation update steps when preparing your branch for merging into the main branch.

What do I need to set up before automating release workflows with GitHub?▼

Before automating release workflows with GitHub, you need the GitHub CLI installed and access to the target repository. This environment setup allows the automation to manage version control tasks, execute tests, and create pull requests on your behalf.

What is the best way to prepare a feature branch for merging into the main branch?▼

The best way to prepare a feature branch for merging is to run an automated release workflow that sequences testing, reviewing, and committing. This ensures all necessary version control checks are completed before the final push and pull request creation.

Does this release automation work without the GitHub CLI?▼

No, this release automation requires the GitHub CLI to execute version control operations and create pull requests. Without the GitHub CLI and repository access, the automated merge, test, and push workflow cannot function.