ship

Automate release workflows by running tests, reviewing diffs, and creating PRs.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill ship-tyhuffman7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-ship
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill ship-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release toil and human error are reduced by automating the entire shipping workflow. This Skill orchestrates base-branch detection, tests, diff review, version bumping, changelog updates, commits, pushes, and PR creation to ship code reliably.

Core Features & Use Cases

  • Deterministic release flow: Detects base branch, runs tests, reviews diffs, bumps VERSION, updates CHANGELOG, commits, pushes, and creates PRs.
  • Governance and traceability: Maintains a clean release history and consistent process across teams.
  • Proactive shipping: Invokes the release sequence when asked to deploy or push to main, reducing manual toil.

Quick Start

Ask me to ship your current branch and I will run the full release flow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my git release workflow from testing to PR creation?

Automating your git release workflow involves detecting the base branch, running tests, reviewing diffs, bumping versions, updating changelogs, and creating PRs. This deterministic flow reduces manual toil and ensures consistent, auditable releases across teams.

What is a deterministic release flow for shipping code?

A deterministic release flow for shipping code is a standardized, auditable sequence that detects the target base branch, runs tests, reviews diffs, bumps the version, updates the changelog, commits, pushes, and creates a PR to ensure reliable deployments.

Can I trigger an automated code review and deploy by just asking to ship a branch?

Yes, you can trigger an automated code review and deploy sequence by simply asking to ship, deploy, or push your current branch to main. The system proactively invokes the entire release sequence including tests, version bumping, and PR creation.

What is the best way to ensure consistent releases and reduce human error across environments?

The best way to ensure consistent releases and reduce human error is to use an automated release orchestration system. It governs the entire process from base-branch detection to PR creation, maintaining traceability and a clean release history across teams.

How does automated version bumping and changelog updating work during a release?

Automated version bumping and changelog updating work by reviewing branch diffs during the release flow. The system automatically increments the VERSION file and appends relevant changes to the CHANGELOG before committing and pushing the code.

Do I need any specific CI tools or dependencies to run the automated shipping sequence?

No specific CI tools or dependencies are required to run the automated shipping sequence. The flow independently detects the base branch, runs tests, reviews diffs, and handles versioning and PR creation without external component dependencies.