ship

Automate software release workflows from quality gates to merge readiness.

7|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/floeorg/floe --skill ship-floeorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/floeorg/floe/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/floeorg/floe --skill ship-floeorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run quality gates, /simplify, /rulify, create or update a PR, poll CI, then mark ready.

Core Features & Use Cases

  • Automates end-to-end ship workflow: quality gates, code review, PR creation, CI loop, merge wait, and land.
  • On re-runs for existing PRs, resumes the CI and merge loop without creating a new PR.
  • Use Case: When a feature branch is ready, ship ensures a complete release pipeline from validation to merge.

Quick Start

Run the ship workflow on the current feature branch to trigger PR creation, quality gates, and CI loops.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate PR creation and CI loops for a feature branch?

To automate PR creation and CI loops, run the ship workflow on your feature branch. It orchestrates quality gates, code review, PR creation, CI polling, and merge readiness in a single end-to-end pipeline.

What happens if I re-run the ship workflow on a branch with an existing PR?

When you re-run the ship workflow on a branch with an existing PR, it resumes the CI and merge loop without creating a new PR, automatically updating the existing pull request.

How does the ship workflow handle quality gates and code simplification?

The ship workflow handles quality gates by running automated checks alongside /simplify and /rulify processes. This ensures code review and release readiness before creating a PR and polling CI.

Can I trigger the ship workflow automatically when a task is completed?

Yes, you can trigger the ship workflow automatically on task completion or via explicit commands like "ship" or "ship it". It also uses argument hints to infer related issue numbers.

What is the best way to coordinate release readiness for ongoing software tasks?

The best way to coordinate release readiness is using an automated ship workflow that manages validation, PR updates, and CI loops. It handles ongoing tasks requiring release pipelines without manual intervention.