ship

Automates ship workflow from merge to PR creation using gstack toolkit.

Updated Mar 30, 2026

Search Tags:#release #pr #deploy #ship #ci #version

Ready to run

npx skills add https://github.com/nhattran998/personal-athlete-agent --skill ship-nhattran998

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/nhattran998/personal-athlete-agent/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/nhattran998/personal-athlete-agent --skill ship-nhattran998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship code quickly by automating the full release workflow from base-branch merge to PR creation, reducing manual handoffs and human errors.

Core Features & Use Cases

Automated merge & diff review: merges the correct base branch, analyzes diffs, and surface changes for review.
Version bump & changelog update: increments the VERSION and updates CHANGELOG consistently.
CI, test, commit, push, and PR creation: runs tests, commits changes, pushes to the target branch, and opens a PR while respecting safety constraints.
Proactive shipping prompts: can be invoked when user asks to ship or deploy, without performing automatic pushes or PRs.

Quick Start

Tell me to ship when your code is ready, and I will run the full workflow to merge, test, tag, and open a PR.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate creating a PR and running tests before deploying code?▼

To automate creating a pull request and running tests before deploying code, you can trigger an end-to-end ship workflow that merges the base branch, runs tests, reviews diffs, and opens a PR safely without direct pushes.

What is the best way to bump versions and update a changelog when pushing to main?▼

The best way to bump versions and update a changelog when pushing to main is to use an automated release workflow that increments the VERSION file, updates the CHANGELOG, commits the changes, and pushes them to the target branch.

Does the automated ship workflow push code directly to the main branch?▼

No, the automated ship workflow avoids direct pushes or pull requests unless explicitly instructed by the user, ensuring that code deployment and branch merges respect safety constraints during the CI process.

Can I review code diffs before a version bump and PR creation?▼

Yes, you can review code diffs before a version bump and PR creation because the ship workflow merges the correct base branch and analyzes diffs to surface changes for review prior to committing and pushing.

When do I need to run an automated release workflow for CI and deployment?▼

You need to run an automated release workflow for CI and deployment when your code is ready for shipping, allowing the system to manage test execution, version increments, changelog updates, and pull request creation.

How to merge the base branch and run tests before opening a pull request?▼

To merge the base branch and run tests before opening a pull request, invoke the ship command when your code is ready, and the workflow will orchestrate merging, testing, tagging, and PR creation end-to-end.