ship

Automate code shipping with base branch detection, tests, version bumping, and PR creation.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/a29paul/hexlens --skill ship-a29paul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/a29paul/hexlens --skill ship-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the error-prone manual work of tracking shipping steps, running pre-merge checks, and creating pull requests, reducing missed steps and release mistakes for development teams.

Core Features & Use Cases

  • Automated Base Branch Detection: Automatically identifies the target merge branch and runs pre-merge tests before proceeding.
  • End-to-End Shipping Workflow: Handles version bumping, changelog updates, commits, pushes, and PR creation in a single guided flow.
  • Proactive Guardrails: Includes telemetry, routing checks, and upgrade prompts to keep your shipping process consistent and up to date. Use Case: A developer who just finished a feature can run this skill to handle all shipping steps without remembering to run tests, update documentation, or create a PR manually.

Quick Start

Use the ship skill to merge your current feature branch into the default base branch, run all tests, update the changelog, and create a pull request for team review.

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 and pre-merge tests?

You can automate pull request creation by running a workflow that detects the base branch, executes pre-merge tests, and generates the PR automatically. This ensures consistent validation before merging feature branches.

What is an end-to-end release workflow for shipping code?

An end-to-end release workflow handles base branch detection, test execution, version bumping, changelog updates, commits, pushes, and pull request creation in a single guided flow to eliminate manual step tracking.

How do I safely merge feature branches without missing deployment steps?

To safely merge feature branches, use an automated shipping process that applies pre-merge validation, routing checks, and guardrails. This ensures compliance with team shipping rules and prevents missed release steps.

Can I automatically update changelogs and bump versions before pushing code?

Yes, you can automatically update changelogs and bump versions before pushing code. The automated workflow handles these updates alongside commits and pushes to ensure your release process remains consistent.

What is the best way to handle merge automation for consistent code deployment?

The best way to handle merge automation is using a guided workflow that integrates diff review, version bumping, and PR creation. This enforces pre-merge validation and maintains consistent release processes.