ship

Automate pre-merge ship workflows for feature branches with tests, version bumps, and PR creation.

48|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/g4rcez/dotfiles --skill ship-g4rcez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/g4rcez/dotfiles/tree/main/.ai/skills/ship
Command: npx skills add https://github.com/g4rcez/dotfiles --skill ship-g4rcez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow automates the end-to-end process of preparing and delivering code changes to production via PRs, removing manual steps and reducing risk.

Core Features & Use Cases

  • Pre-flight checks including base branch detection
  • Merge base into feature branch and run tests in parallel
  • Auto-eval suites, pre-landing review, and changelog generation
  • Auto version bump decisions and CHANGELOG updates
  • Create PR and push, with explicit non-interactive flow

Quick Start

Run the /ship command on your feature branch to trigger the fully automated ship workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate changelog generation and version bumping before creating a PR?

Automate changelog generation and version bumping by triggering a fully automated ship workflow that executes tests, performs pre-landing review, updates the changelog, bumps versions, and creates the PR without manual intervention.

What is an automated end-to-end ship workflow for feature branches?

An automated end-to-end ship workflow reduces manual toil by detecting the base branch, merging it into your feature branch, running tests in parallel, auto-versioning, generating changelogs, and pushing a ready PR.

Can I run tests and merge the base branch into my feature branch automatically?

Yes, the automated ship workflow merges the base branch into your feature branch and runs tests in parallel as part of its pre-merge checks to ensure your code is ready before PR creation.

Does the automated ship workflow require human interaction during the PR creation process?

No, the automated ship workflow operates as an explicit non-interactive flow, handling pre-flight checks, version bumps, changelog updates, and PR creation entirely without human intervention.

What are the limitations of using a non-interactive workflow for CI and version bumps?

The non-interactive ship workflow is designed strictly for pre-merge scenarios where tests pass automatically, meaning it may not suit contexts requiring manual approval gates or interactive conflict resolution during base branch merges.