ship

Merge base branches, run tests, bump version, update changelog, and create PRs.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill ship-txema-puch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/txema-puch/drone-ai-saturdays/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/txema-puch/drone-ai-saturdays --skill ship-txema-puch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end shipping workflow: detect the base branch, merge into the feature branch, run the test suite, bump the version, update CHANGELOG, commit, push, and create a PR. It helps teams move finished work from development to release with minimal manual friction.

Core Features & Use Cases

  • Auto-merge base branch and run tests against the merged state to ensure compatibility.
  • Bump VERSION, update CHANGELOG, and prepare a clean release commit.
  • Create, push, and open a PR from the feature branch with a clear summary of changes.
  • Proactively suggest when deployment or release is appropriate based on the code status.

Quick Start

Ship the current branch to a PR-ready state.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate creating a pull request and updating the changelog for a feature branch?

Automating pull request creation and changelog updates involves merging the base branch, running tests, bumping the version, and committing changes before pushing to open a PR. This approach ensures release-ready code with minimal manual friction.

What is an end-to-end release workflow for shipping code changes from a feature branch?

An end-to-end release workflow detects the base branch, merges it into your feature branch, runs the test suite, updates versioning and changelogs, and creates a PR. It moves finished development work to a release-ready state automatically.

Do I need a clean git history before automating a pull request release workflow?

Yes, automating a pull request release workflow requires a clean git history and repository access. These prerequisites are necessary for the tool to perform diffs, create commits, update versioning, and push your feature branch successfully.

Does automated release shipping run tests against the merged base branch state?

Yes, automated release shipping runs tests against the merged base branch state. Auto-merging the base branch into your feature branch before testing ensures compatibility and verifies that your code changes work with the latest main branch updates.

What's the best way to prepare a feature branch for a release commit without manual friction?

The best way to prepare a feature branch for a release commit is to automate merging the base branch, bumping the VERSION file, and updating the CHANGELOG. This creates a clean release commit and opens a PR with a clear summary of changes.

Why should I not use automated CI-CD shipping for my current git branch?

You should not use automated CI-CD shipping if your git history is unclean or if you lack direct repository access. The automation requires a clean state to perform diffs, commit versioning updates, and push your feature branch without conflicts.