ship

Automate branch synchronization, multi-suite testing, and pull request creation.

1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill ship-gth-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/gth-ai/hadriengayap.github.io/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill ship-gth-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead and human error associated with the software release process, ensuring that every deployment is tested, reviewed, and documented consistently.

Core Features & Use Cases

  • Automated Release Pipeline: Orchestrates merging, testing, version bumping, and changelog generation in a single command.
  • Pre-Landing Safety: Performs automated structural reviews and eval-based regression testing for prompt-related changes.
  • Use Case: When a feature branch is ready for production, use this Skill to automatically merge main, run parallel test suites, generate a versioned changelog, and create a pull request with a comprehensive summary.

Quick Start

Run the ship workflow to automatically merge, test, and create a pull request for your current feature branch.

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 with branch synchronization and pull request creation?

Automate your git release workflow by orchestrating branch synchronization, multi-suite testing, and pull request creation in a single command. This ensures every deployment is tested, reviewed, and documented consistently without manual overhead.

What's the best way to run pre-merge validation and automated versioning for a feature branch?

Pre-merge validation and automated versioning are handled by applying rigorous release gates to your feature branch. The process automatically merges main, runs parallel test suites, bumps versions, and generates a versioned changelog before landing.

Do I need the gh CLI and local test runners to execute an automated deployment pipeline?

Yes, you need git, the gh CLI, and local test runners installed to execute the full release gate. These tools are required to perform branch synchronization, multi-suite testing, and automated pull request creation successfully.

How does automated regression testing work for prompt-related changes before landing code?

Automated regression testing for prompt-related changes works by performing eval-based testing during the pre-landing phase. This structural review validates changes against expected behavior before merging, ensuring high-integrity deployments.

Can I generate a versioned changelog and comprehensive pull request summary automatically?

Yes, you can automatically generate a versioned changelog and comprehensive pull request summary. The release pipeline orchestrates these documentation steps alongside merging and testing to standardize your deployment records.

When should I not use an automated release pipeline for software deployment?

You should avoid automated release pipelines for software deployment when your project lacks local test runners or the gh CLI. Without these dependencies, the rigorous pre-merge validation and automated versioning gates cannot execute properly.