ship

Orchestrate Git ship workflows from base-branch detection to PR creation.

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

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", "create a PR", "merge and push", or get it deployed.

Core Features & Use Cases

  • Automates the full ship lifecycle: detect base branch, run tests, review diffs, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Proactive workflow invocation: proactively guide deployment steps when asked to ship or deploy.
  • Guardrails and auditable process: ensures PR-based deployment and maintains an auditable history.

Quick Start

Ask me to ship by saying ship it and I will orchestrate the PR, tests, and deployment steps.

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 PR with tests and changelog updates before pushing to main?

The ship workflow automates the full PR lifecycle by detecting the base branch, running tests, bumping the VERSION, updating the CHANGELOG, and opening a PR to ensure safe deployment.

What is the safest way to manage version bumps and changelog updates for feature branches?

The safest way is using an automated ship workflow that prompts for actions, reviews diffs, and updates the CHANGELOG and VERSION files before pushing your feature branch to a remote repository.

Can I use this ship workflow to merge my base branch and run CI tests before deployment?

Yes, the ship workflow explicitly handles base-branch detection and merging, runs tests, and ensures CI steps are completed before committing and pushing code to main.

What's the best way to ensure an auditable deployment history when pushing code?

Enforcing a PR-based deployment workflow with automated changelog updates and version bumping ensures an auditable history by prompting for actions and completing steps before pushing to main.

Do I need to manually update the CHANGELOG and VERSION files when shipping code?

No, the ship workflow automatically bumps the VERSION and updates the CHANGELOG during the commit phase, ensuring these files are always current before creating the pull request.