ship

Automate the release workflow from base-branch detection to PR creation.

5|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill ship-drt0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-ship
Command: npx skills add https://github.com/drt0927/tw-overlay --skill ship-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines releasing software by performing the full ship workflow automatically—from base-branch detection to PR creation—eliminating manual handoffs and reducing release cycle time.

Core Features & Use Cases

  • End-to-end release automation: detect the base branch, run tests, review diffs, bump the VERSION, update CHANGELOG, commit, push, and open a PR.
  • Proactive shipping: trigger the workflow when the user signals readiness or requests deployment, avoiding manual confirmations.
  • Consistent, auditable releases: ensures versioning, changelog updates, and PR history are uniform across teams and repos.

Quick Start

Run the /ship workflow to automatically complete the release process from a feature branch to a PR on the base branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a git release workflow from start to finish?

Automating a git release workflow is done by detecting the base branch, running tests, bumping the VERSION, updating the CHANGELOG, and opening a PR. This end-to-end automation eliminates manual handoffs and reduces release cycle time.

What is the best way to bump versions and update changelogs automatically?

Bumping versions and updating changelogs automatically happens by reviewing diffs within the git workflow. It ensures versioning and changelog updates are uniform across teams and repos, creating a consistent and auditable release history.

How do I create a pull request for deployment without manual confirmations?

Creating a pull request for deployment without manual confirmations is triggered when you signal readiness. The workflow proactively pushes commits and opens a PR on the base branch, avoiding manual confirmations entirely.

Do I need a gstack runtime to automate end-to-end release workflows?

Automating end-to-end release workflows requires a gstack runtime to orchestrate the steps. You also need a Git repository setup and remote access to execute the tests, commits, and PR creation successfully.

Can I use PR-based releases for codebases with shared standards?

PR-based releases for codebases with shared standards are fully supported. The workflow detects the base branch, reviews diffs, and ensures versioning and changelog updates remain uniform across teams and repositories.

Why does my automated release workflow require remote access?

Automated release workflows require remote access to push commits and create the pull request on the base branch. Without it, the gstack runtime cannot orchestrate the final steps of the end-to-end release process.