skills.rest
Bradliebs
BradliebsCOMMUNITY
Explore all skills by this author →
GitHub

ship

Orchestrate Git release workflows with tests, diff review, and PR creation.

Updated Mar 14, 2026
Search Tags:#automation#git#versioning#release#pr#ship#ci
One-click install
npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ship-bradliebs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.gstack/ship
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ship-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow for software projects: merging base branches, running tests, reviewing diffs, bumping VERSION, updating CHANGELOG, committing changes, pushing, and creating PRs.

Core Features & Use Cases

  • Base-branch merge, test orchestration, and diff reviews to ensure release readiness.
  • Version bumping and CHANGELOG updates to reflect new releases.
  • PR creation and automated preflight checks to streamline shipping.

Quick Start

Trigger the ship workflow when your code is ready to be released to main and let it handle tests, reviews, and PR creation.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate my Git release workflow from running tests to creating a PR?▼

Automating a Git release workflow involves orchestrating base-branch merging, test execution, diff reviews, version bumping, changelog updates, and PR creation into a single pipeline. This ensures release readiness and streamlines shipping code to main.

Can I automatically update the changelog and bump versions before creating a pull request?▼

Yes, you can automatically update the changelog and bump the VERSION file before creating a pull request. Automating these steps ensures your release documentation accurately reflects new changes before the PR is opened.

What is the best way to ensure release readiness before merging code to the main branch?▼

The best way to ensure release readiness is running automated preflight checks that merge the base branch, execute tests, and review diffs. This validates your codebase and confirms everything passes before pushing changes.

Do I need any external CI dependencies to automate versioning and pull request creation?▼

No external CI dependencies are required to automate versioning and pull request creation. The workflow independently orchestrates Git operations, commits, and PR creation directly within your repository environment.

When should I use an automated release orchestration workflow instead of manual Git commands?▼

You should use automated release orchestration when your codebase is ready for release and you need consistent validation, changelog maintenance, and PR pipelines. It replaces manual Git commands to eliminate human error during repetitive shipping tasks.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

ship

Prepare feature branches for release with tests, versioning, and pull requests.

Official
Advanced
ITSaltITSalt
23

nacl-tl-release

Automate end-to-end software releases by merging PRs, validating CI, and publishing changelogs.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
BagelHoleBagelHole
46

semantic-versioning

Automate version bumps and changelog generation from Conventional Commits.

Community
Advanced