gstack-ship

Automates the ship workflow of testing, versioning, committing, pushing, and creating pull requests.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-ship-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-ship
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/gstack-ship
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-ship-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code involves a repetitive, error-prone sequence: merging the base branch, running tests, reviewing the diff, bumping the version, updating the changelog, committing, pushing, and opening a PR. This Skill orchestrates that entire release workflow so nothing gets skipped. ## Core Features & Use Cases - End-to-End Ship Pipeline: Detects and merges the base branch, runs tests, reviews the diff, bumps VERSION, updates CHANGELOG, commits, pushes, and creates a PR in one guided flow. - Interactive Decision Gates: Uses structured AskUserQuestion decision briefs with recommendations, pros/cons, and completeness scores before irreversible actions. - Context and Checkpoint Integration: Recovers recent project artifacts, supports continuous WIP checkpoint commits, and squashes them into clean commits at ship time. - Use Case: A developer finishes a feature branch and says "ship it" — the Skill runs the full release checklist, confirms key decisions, and ends with an open pull request. ## Quick Start Ask the assistant to ship the current branch and create a pull request using the gstack-ship skill.

Frequently Asked Questions about gstack-ship

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

FAQPage Schema
How do I ship code and create a pull request automatically?▼

Invoke the ship workflow by saying "ship it", "create a PR", or "push to main". The skill merges the base branch, runs tests, reviews the diff, bumps VERSION, updates the CHANGELOG, commits, pushes, and opens the pull request.

What steps does an automated ship workflow run before creating a PR?▼

It detects and merges the base branch, runs the test suite, reviews the diff for issues, bumps the version number, updates the changelog, then commits and pushes before opening the PR. Each high-stakes step can require confirmation through a decision prompt.

Can the ship skill run in plan mode or spawned sessions?▼

Yes. In plan mode the skill's instructions take precedence and its first AskUserQuestion counts as entering plan mode. In spawned orchestrator sessions it skips interactive prompts, auto-chooses recommended options, and ends with a completion report.

Why is the ship skill blocked with an AskUserQuestion error?▼

The workflow depends on an AskUserQuestion tool variant, either a host MCP version or the native one. If neither is available in the tool list, the skill stops and reports BLOCKED rather than silently auto-deciding.

What happens to WIP checkpoint commits when shipping?▼

If continuous checkpoint mode created WIP-prefixed commits during development, the ship workflow squashes them into clean commits as part of finalizing the branch for the pull request.