ship

Automate the software ship workflow from branch detection to pull request creation.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/DaviRain-Su/sui-zig-rpc-client --skill ship-davirain-su
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/DaviRain-Su/sui-zig-rpc-client/tree/main/.agents/skills/gstack-ship
Command: npx skills add https://github.com/DaviRain-Su/sui-zig-rpc-client --skill ship-davirain-su

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the full shipping process of a software development workflow, from testing to merging and creating pull requests, to reduce manual steps and increase efficiency.

Core Features & Use Cases

  • Branch Detection: Automatically detects the base branch for pull requests.
  • Test Execution: Executes tests and checks for merge conflicts or test failures.
  • Code Review: Facilitates code reviews and suggests when review is complete.
  • Version Management: Automatically manages version numbers and CHANGELOG updates.
  • PR Creation: Automatically creates pull requests for code merges.
  • Use Case: Use this Skill to ensure that a new feature is fully tested, reviewed, and ready for merging into the main codebase before creating a pull request.

Quick Start

To start the ship workflow, use the command: gstack ship

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my CI/CD ship workflow for version control and pull requests?▼

Automate your CI/CD ship workflow by running `gstack ship` to automatically detect the base branch, execute tests, perform code reviews, bump versions, and create pull requests.

What is the best way to automate code review and version bumping before merging?▼

Automating code review and version bumping is handled by the ship workflow, which facilitates reviews, suggests completion, and automatically manages version numbers and CHANGELOG updates before merging.

Do I need git and gstack to automate the end-to-end software development ship workflow?▼

Yes, you need git and gstack to automate the end-to-end ship workflow, along with various build and test tools to execute tests and handle runtime frameworks during CI/CD pipeline execution.

How does automated branch detection work when creating a pull request?▼

Automated branch detection works by identifying the correct base branch for your code merges during the ship workflow, ensuring pull requests are accurately targeted before execution and review.

Can I run automated tests and check for merge conflicts in my CI/CD pipeline?▼

Yes, you can run automated tests and check for merge conflicts directly within your CI/CD pipeline using the ship workflow, which executes tests and identifies failures before creating pull requests.

What are the limitations of automating software development shipping with gstack?▼

Limitations of automating software development shipping include dependencies on git, gstack, and specific build or test tools, requiring proper runtime framework configuration to execute tests and merge code successfully.