ship

Automate code release workflows from merge to pull request creation.

5|2|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/agatx/serenada --skill ship-agatx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/agatx/serenada/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/agatx/serenada --skill ship-agatx

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ship workflow automation resolves the manual toil of releasing code by coordinating base-branch merging, test execution, version bumps, changelog updates, commits, pushes, and PR creation in a single streamlined process.

Core Features & Use Cases

  • End-to-end release automation: Merge the base branch, run tests, generate diffs, bump VERSION, update CHANGELOG, commit, push, and open a PR.
  • Proactive deployment readiness: Suggests optimal deployment timing and pre-merge checks when requested.
  • Use Case: A developer finishes a feature and says “ship” to automatically prepare a PR with all release artifacts and notes.

Quick Start

Trigger the full ship workflow by running the /ship command to merge base, execute tests, update versioning, and create 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 my git workflow from running tests to creating a PR?▼

Automating your git workflow streamlines the release process by merging the base branch, running tests, bumping versions, updating changelogs, and creating a PR automatically in a single command.

What is the best way to update a changelog and version before opening a release PR?▼

Updating a changelog and version before opening a release PR is handled automatically during the ship workflow, which generates diffs, applies version bumps, and commits the release artifacts alongside the PR creation.

Do I need a configured CI environment to automate creating a pull request?▼

You need a configured git environment and CI readiness to automate creating a pull request, ensuring the workflow can successfully push commits and execute the necessary test suites before deployment.

Can I merge the base branch and run tests in one automated release workflow?▼

Merging the base branch and running tests in one automated release workflow is fully supported, coordinating these pre-merge checks sequentially before updating versioning and pushing the final pull request.

When should I use an end-to-end release automation workflow?▼

Use an end-to-end release automation workflow when you finish a feature and need to prepare a pull request with all release artifacts, or when you need proactive deployment timing suggestions and pre-merge validation.

Why does my automated release workflow suggest optimal deployment timing?▼

An automated release workflow suggests optimal deployment timing to provide proactive deployment readiness, helping you determine the best moment to merge code based on pre-merge checks and test execution results.