skills.rest
ComputerConnection
ComputerConnectionCOMMUNITY
Explore all skills by this author →
GitHub

ship

Automate release workflows by merging, testing, reviewing diffs, bumping versions, and opening pull requests.

Updated Mar 31, 2026
Search Tags:#automation#versioning#release-management#ci-cd#git-workflow#pull-request
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill ship-computerconnection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/gstack-ship
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill ship-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the end-to-end shipping process for code changes, removing manual steps from review to PR creation.

Core Features & Use Cases

  • Detect and merge the base branch, run the full test suite, review diffs, bump the version, update the CHANGELOG, commit, push, and open a PR.
  • Works for standard release flows and can proactively suggest when a change is ready to ship or deploy.
  • Provides an auditable trail of changes and ensures consistency across releases.

Quick Start

Say "ship this change" to trigger the full automated workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the release workflow from testing to pull request creation?▼

Automating the release workflow involves merging the base branch, running tests, bumping the version, updating the changelog, and pushing to open a pull request. This process removes manual steps from code review to PR creation.

How do I know if my code changes are ready to ship?▼

You can determine if changes are ready to ship by running the full test suite and reviewing the git diff. The workflow proactively suggests deployment readiness based on passing test results and diff analysis.

What do I need to set up before automating a git workflow for shipping?▼

Before automating a git workflow, you need access to the repository, configured test suites, and a remote origin set up. These components ensure the end-to-end shipping process runs deterministically.

Does automated version bumping also update the changelog?▼

Yes, automated version bumping also updates the changelog. The workflow handles both tasks sequentially before committing and pushing the changes to create an auditable trail of updates.

Can I use this for standard release flows without a complex CI-CD pipeline?▼

Yes, you can use this for standard release flows without a complex CI-CD pipeline. It works for standard release processes by managing the git workflow locally before opening a pull request.

Why should I use an automated ship workflow instead of manual pull requests?▼

An automated ship workflow ensures consistency across releases and provides an auditable trail of changes. It removes manual steps from merging the base branch to PR creation, reducing human error.

Related Skills

Explore More Software Engineering Skills→
HenquewlHenquewl
7

finishing-a-development-branch

Verify test suites and finalize git development branches through merge or cleanup.

Community
Advanced
CODE-SAURABHCODE-SAURABH
2

land-and-deploy

Merge approved pull requests and verify production health after deployment.

Community
Advanced
joeylife94joeylife94

ship

Automate code deployment with branch detection, tests, version bump, and pull request creation.

Community
Advanced
akiojinakiojin
4

release

Automate version updates, changelog generation, and release pull requests from develop to main.

Community
Advanced