ship

Automate the ship workflow from code readiness to merge request creation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gfires/motion-analysis --skill ship-gfires
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/gfires/motion-analysis/tree/main/ship
Command: npx skills add https://github.com/gfires/motion-analysis --skill ship-gfires

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ship workflow orchestration for software teams: detect base branch, run tests, review diffs, bump version, update changelog, commit, push, and create PR. This reduces manual handoffs and ensures consistent release discipline.

Core Features & Use Cases

  • End-to-end automation of a ship/deploy pipeline across branches and PRs.
  • Deterministic execution of tests, reviews, and versioning to produce ready-to-merge PRs.
  • Use Case: When a feature is ready, run the full ship flow to generate a PR with changes and changelog updates.

Quick Start

Say 'ship this feature' to trigger the full automated workflow.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate end-to-end ship workflows from code to PR?

Automate ship workflows by triggering the full pipeline to detect base branches, run tests, review diffs, bump versions, update changelogs, and push merge requests. This produces ready-to-merge PRs with all metadata.

What is the best way to create a ready-to-merge PR with automated versioning and changelog updates?

Creating a ready-to-merge PR with automated versioning is handled by deterministically executing tests, diff reviews, version bumps, and changelog updates before pushing. This ensures consistent release discipline across feature branches.

How does automated base-branch detection and test execution work for feature branches?

Automated base-branch detection and test execution work by deterministically executing each pipeline step on feature branches in standard CI/CD environments. The workflow handles conflicts and re-runs as needed to ensure code passes quality gates.

Can I use automated ship workflow orchestration for feature branches in standard CI/CD environments?

Automated ship workflow orchestration applies to feature branches in standard CI/CD environments where code must pass tests, approvals, and quality gates before merging. It reduces manual handoffs while ensuring consistent release discipline.

How do I trigger the full automated ship flow to generate a PR?

Trigger the full automated ship flow to generate a PR by saying 'ship this feature'. This executes the complete workflow from code readiness to PR creation, including diff reviews and changelog updates.

What happens when automated diff reviews and version bumps encounter conflicts during the ship pipeline?

When automated diff reviews and version bumps encounter conflicts during the ship pipeline, the workflow deterministically handles conflicts and re-runs as needed. This ensures the final merge request contains validated, ready-to-merge code.