ship

Orchestrate software shipping from base-branch detection to PR creation.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill ship-lemig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/lemig/transcriptor --skill ship-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", or "get it deployed". (gstack)

Core Features & Use Cases

  • Detect base branch, run tests, generate diffs, bump VERSION, update CHANGELOG, commit, and push changes
  • Proactively prompt to create a PR or deploy, ensuring code is release-ready and auditable
  • Works across typical CI/CD workflows, preserving safety and traceability

Quick Start

Ship the current feature branch to main after tests pass.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git releases with changelog and version updates?

Automating git releases involves detecting the base branch, running tests, bumping the VERSION file, updating the CHANGELOG, and pushing changes. This Skill orchestrates that entire workflow and proactively prompts you to create a PR for deployment.

What is the best way to bump VERSION and update CHANGELOG before creating a PR?

Bumping VERSION and updating CHANGELOG before a PR is handled by an automated release workflow. This Skill runs tests, reviews diffs, updates both files, commits, and pushes the changes before prompting you to create a deployment PR.

Can I use this automated release workflow with my existing CI/CD pipelines?

You can use this automated release workflow with existing CI/CD pipelines. It integrates into typical CI/CD workflows by automating base-branch detection, test runs, version bumps, and PR creation while preserving deployment safety and traceability.

How does automated base-branch detection work for pushing code to main?

Automated base-branch detection identifies the target branch, merges changes, and runs tests before versioning. This ensures your code is properly validated and release-ready before you push to main or create a deployment PR.

Do I need to manually trigger PR creation after version bumps and changelog updates?

You do not need to manually trigger PR creation after version bumps and changelog updates. The Skill proactively prompts you to create a PR or deploy once the automated changes are committed and pushed to your repository.