skills.rest
gebl
geblCOMMUNITY
Explore all skills by this author →
GitHub

ship

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

1|Updated Mar 27, 2026
Search Tags:#automation#workflow#pr#ship#ci#version-bump
One-click install
npx skills add https://github.com/gebl/anvil-skill-marketplace --skill ship-gebl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/gebl/anvil-skill-marketplace/tree/main/generated/claude/skills/ship
Command: npx skills add https://github.com/gebl/anvil-skill-marketplace --skill ship-gebl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow automates the end-to-end process of taking code from a prepared state to a PR-ready commit. It orchestrates base-branch detection, test execution, diff review, version bump, CHANGELOG updates, commit, push, and PR creation, ensuring consistent releases and reduced manual toil.

Core Features & Use Cases

  • End-to-end ship automation: detect the base branch, run tests, review changes, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Proactive guidance: suggests when to ship and ensures changes are ready for review in CI environments.
  • Reliable hand-off: works across common branching strategies and teams to produce predictable PRs.

Quick Start

Initiate an automated ship flow on the current branch to generate a PR-ready change set.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the end-to-end ship workflow from running tests to PR creation?▼

To automate the ship workflow, you need a tool that orchestrates base-branch detection, tests, diffs, version bumps, changelog updates, commits, pushes, and PR creation into a deterministic process that generates PR-ready changes.

What is the best way to manage version bumps and changelog updates before pushing a PR?▼

Managing version bumps and changelog updates requires an automated workflow that detects the base branch, reviews the diff, bumps the VERSION file, updates the CHANGELOG, and commits the changes before pushing to open a PR.

Does automated PR creation work with common branching strategies and CI setups?▼

Automated PR creation works across common branching strategies and CI setups by orchestrating tests, version bumps, and commits to produce predictable PRs for collaborative software shipping scenarios.

When do I need an automated ship workflow for my code deployment?▼

You need an automated ship workflow when your code is ready for deployment or review, ensuring consistent releases and reduced manual toil by automating tests, versioning, changelog updates, and PR creation.

Can I use a single tool to detect the base branch, run tests, and create a PR?▼

You can use an end-to-end ship automation tool to detect the base branch, run tests, review changes, bump versions, update changelogs, and create a PR, ensuring a reliable hand-off for code review.

Related Skills

Explore More Software Engineering Skills→
him55710-sudohim55710-sudo

ship

Automate code shipping with tests, version bumps, and PR creation.

Community
Advanced
D0NMEGAD0NMEGA
8

gsd-ship

Push a branch, create a PR with an auto-generated body, and track merge status.

Community
Advanced
pistosminpistosmin

ship

Automate the ship workflow from branch merge to PR creation.

Community
Advanced
gannonhgannonh
1

releasing-kata-agents

Guide Kata Agents release workflows with version bumps, changelogs, and release PRs.

Community
Advanced