skills.rest
mi179
mi179COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Automate release workflows by running tests, updating versions, and creating pull requests.

1|Updated May 27, 2026
Search Tags:#automation#git#workflow#testing#release#ship#pull-request
One-click install
npx skills add https://github.com/mi179/claude-skills --skill ship-mi179
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/ship
Command: npx skills add https://github.com/mi179/claude-skills --skill ship-mi179

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow by detecting the base branch, running the test suite, and preparing a safe merge.

Core Features & Use Cases

  • Detects the current base branch, runs the test suite, and prepares a merge-ready state for release.
  • Updates version and CHANGELOG, commits changes, pushes, and creates a PR to formalize the release.
  • Use Case: when a feature is ready for deployment, trigger the ship workflow to produce a PR with all release artifacts and notes.

Quick Start

Command a release flow: say "ship this change to main" and have the system prepare and propose a PR with the version bump and CHANGELOG.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate a git release workflow with version bumps and pull requests?▼

You can automate a git release workflow by triggering a command like "ship this change to main," which runs the test suite, updates the version and CHANGELOG, and pushes a pull request instead of deploying directly.

What is the safest way to prepare a merge candidate for code deployment?▼

The safest way to prepare a merge candidate is to use an automated release workflow that performs deterministic, auditable steps and pushes a PR rather than executing a direct deployment to the base branch.

Can I automatically update a CHANGELOG and create a pull request when a feature is ready?▼

Yes, you can automatically update a CHANGELOG and create a pull request by triggering an end-to-end release workflow that prepares all release artifacts and formalizes the merge through a PR.

Does the automated release workflow run tests before pushing a merge to the base branch?▼

Yes, the automated release workflow runs the test suite and detects the current base branch to prepare a merge-ready state before committing changes and pushing the pull request.

Why should I use a PR workflow instead of direct deployment for releasing changes?▼

You should use a PR workflow instead of direct deployment because it enforces safe operations through deterministic, auditable steps, ensuring changes are formally reviewed before merging to the base branch.

Related Skills

Explore More Software Engineering Skills→
putrawitamaputrawitama
1

ship

Automate Git release workflows from code completion to pull request readiness.

Community
Advanced
forbotsakeforbotsake
5

ship

Automate release workflows from base-branch detection to pull request creation.

Official
Advanced
involvexinvolvex

changelog-automation

Generate changelogs and release notes from conventional commits.

Community
Intermediate
StaysrStaysr

version-release

Automate version tagging, changelog generation, and PR workflows for minor and patch releases.

Community
Advanced