ship

Automates GitHub PRs, CI checks, and deploys across branches to production.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/benjaminfauchald/Tracklister --skill ship-benjaminfauchald
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/benjaminfauchald/Tracklister/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/benjaminfauchald/Tracklister --skill ship-benjaminfauchald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of promoting code from feature or develop branches into main and deploying those changes to UAT or Production, reducing manual choreography and human error during releases.

Core Features & Use Cases

  • Branch detection and routing: Detects whether you are on a feature, develop, or main branch and follows the appropriate workflow.
  • PR creation and merging: Creates or finds pull requests, waits for required CI checks, and merges with the correct strategy while handling branch protection errors.
  • Deployment orchestration: Triggers UAT or Production workflows, handles tagging for production releases, and polls run status until completion.
  • Use Case: A developer on a feature branch can push changes, let this Skill open or reuse PRs to develop, ensure CI passes, merge through to main, and then deploy to UAT or Production without manual multi-repo commands.

Quick Start

Run the ship procedure from the repository root to push the current branch, create or find the necessary PRs, wait for CI to pass, merge develop into main if required, and then choose UAT or Production to deploy.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate merging a GitHub feature branch into develop and main?▼

Automate merging by running a procedure from the repository root that detects the feature branch, pushes changes, creates or reuses pull requests, waits for CI checks to pass, and merges through develop into main using the correct strategy.

How does branch detection work for release workflows using develop and main?▼

Branch detection identifies whether the current Git reference is a feature, develop, or main branch, automatically routing the workflow to the appropriate PR creation, CI validation, and merge sequence for reliable deployments.

Can I trigger UAT or production deployments after merging pull requests?▼

Yes, after merging pull requests you can trigger UAT or production deployment workflows. The process orchestrates tagging for production releases and polls the GitHub workflow run status until completion.

Does this deployment automation work with GitHub CLI and branch protection rules?▼

Yes, it works with GitHub CLI and handles branch protection by falling back to admin privileges when necessary, ensuring required CI checks pass and managing merge strategies for protected branches.

What happens if required CI checks fail before merging to main?▼

If required CI checks fail, the merge process waits for them to pass before proceeding. The workflow ensures all pull request validation gates are satisfied before attempting to merge into develop or main.