ship

Automate the end-to-end ship workflow from base-branch detection to PR creation.

2|2|Updated Dec 1, 2024
One-click install
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill ship-yaugourt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/ship
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill ship-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow automates the end-to-end shipping process for software projects, eliminating manual coordination from base-branch detection to PR creation.

Core Features & Use Cases

  • Base-branch detection and merge prep
  • Test execution and result aggregation
  • Automatic version bump and CHANGELOG update
  • Commit, push, and PR creation with correct base branch
  • Safe conflict handling and fallbacks for common edge cases

Quick Start

Trigger the ship workflow by asking your AI to ship the current branch.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git pull request creation with changelog updates?

Automating git pull request creation with changelog updates requires a workflow that handles base-branch detection, version bumping, CHANGELOG modifications, committing, pushing, and opening the PR automatically. This eliminates manual coordination for software releases.

What is the best way to handle version bumping and changelog generation before opening a PR?

The best way to handle version bumping and changelog generation before opening a PR is using an automated end-to-end ship workflow. It coordinates git operations, updates the CHANGELOG, commits the changes, and pushes the branch right before creating the pull request.

How does base branch detection work when automating a git ship workflow?

Base branch detection in an automated git ship workflow identifies the correct target branch for your pull request. It ensures the workflow commits, pushes, and opens the PR against the correct base, preventing incorrect branch targeting during releases.

Can I automate tests and merge prep before creating a pull request?

You can automate tests and merge prep before creating a pull request using an end-to-end shipping workflow. It executes tests, aggregates results, applies safe conflict handling fallbacks, and prepares the merge before automatically opening the PR.

What happens if there are git conflicts during automated pull request creation?

If there are git conflicts during automated pull request creation, the workflow applies safe conflict handling and fallbacks for common edge cases. This ensures the ship process stops or adjusts safely rather than overwriting unresolved branch changes.