ship

Automates the end-to-end ship workflow for code changes.

Updated Dec 13, 2017
One-click install
npx skills add https://github.com/dogeared/tnra --skill ship-dogeared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/ship
Command: npx skills add https://github.com/dogeared/tnra --skill ship-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship automation to streamline end-to-end release workflows across base branch, tests, and PRs.

Core Features & Use Cases

  • Automates base-branch merge, test execution, diff review, and version bump
  • Updates CHANGELOG, commits, pushes, and opens a PR for ship-ready changes
  • Proactively suggests shipping when code is ready or deployment is needed

Quick Start

Say 'ship' to trigger an automated end-to-end shipping workflow that merges the base branch, runs tests, updates the version and changelog, commits, pushes, and opens 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 pull-request workflow from merge to push?

Say "ship" to trigger an automated end-to-end shipping workflow that merges the base branch, runs tests, updates the version and changelog, commits, pushes, and opens a PR.

What is the best way to automate versioning and changelog updates before a push?

Automating versioning and changelog updates before a push is handled within a deterministic ship workflow that automatically applies version bumps and documents changes before committing to the base branch.

Can I automatically run tests and merge the base branch before creating a pull request?

Yes, you can automatically run tests and merge the base branch before creating a pull request by initiating a ship workflow that enforces this deterministic sequence prior to pushing code.

Does the automated ship workflow suggest pushing code when changes are ready?

Yes, the automated ship workflow proactively suggests pushing code when repository state indicates changes are ready or when a deployment is needed.

When should I use an automated end-to-end ship workflow for code changes?

Use an automated end-to-end ship workflow for code changes when you need a deterministic sequence to enforce base-branch merges, test execution, diff reviews, and PR creation without manual intervention.