skills.rest
ClyptAI
ClyptAIOFFICIAL
Explore all skills by this author →
GitHub

ship

Automate release flow by merging branches, running tests, bumping versions, and creating pull requests.

Updated Mar 8, 2026
Search Tags:#automation#git#deployment#pr#ship#tests#version
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Backend --skill ship-clyptai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/gstack/ship
Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill ship-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines end-to-end release tasks by automating base-branch merging, test runs, version bumps, changelog updates, commits, and PR creation.

Core Features & Use Cases

  • Detects the base branch and merges changes into it
  • Runs the test suite and reports results
  • Bumps version numbers and updates CHANGELOG
  • Commits changes and creates a pull request
  • Works across branches to prepare a production-ready release
  • Use case: when you want to ship a feature quickly with an auditable release trail

Quick Start

Ask the AI to ship after code review; it will detect the base branch, run tests, bump the version, update the changelog, commit, push, and open a PR.

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 deployment flow from running tests to creating a pull request?▼

Automated git deployment merges changes into the base branch, runs tests, bumps versions, updates the changelog, commits, and opens a PR. This streamlines the end-to-end release flow by coordinating checks and preparing a production-ready diff for review.

What is the best way to prepare a production-ready release across multiple branches?▼

Preparing a production-ready release involves detecting the base branch, merging changes, running test suites, bumping versions, and updating the changelog. This automated release flow ensures your diffs are ready for review before pushing to main.

Does automated release workflow require manual version bumps and changelog updates?▼

Automated release workflows handle version bumps and changelog updates automatically. You do not need to manually update these files; the system enforces these release prerequisites during the commit and pull request creation process.

Can I use automated shipping to push code to main without running tests first?▼

Automated shipping enforces release prerequisites by running the test suite and reporting results before creating a pull request. It coordinates checks across branches to ensure diffs are ready for review, preventing untested code from deploying.

How do I ship code faster with an auditable release trail?▼

Shipping code faster with an auditable trail is achieved by automating base-branch merges, test runs, version bumps, changelog updates, and PR creation. This end-to-end release flow ensures every deployment step is recorded and verified.

When should I not use automated deployment for a pull request?▼

You should avoid automated deployment when your release requires manual intervention outside of standard version bumps and changelog updates. The workflow is designed for standard git release scenarios and enforces specific prerequisites like test runs before opening a PR.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

ship

Automate Git release shipping by merging base branch, testing, updating CHANGELOG, bumping VERSION, and creating a PR.

Community
Advanced
ibalasiteibalasite

ship

Merge a feature branch, run tests, bump VERSION, update CHANGELOG, and create a pull request.

Community
Advanced
mcampbellrmcampbellr

gsd-ship

Create pull requests and trigger code reviews after verification passes.

Community
Intermediate
VertaKhanVertaKhan

ship

Automate release workflows from feature branch to pull request.

Community
Advanced