ship

Commit Minerva work, push a branch, and open a GitHub PR with CI checks.

Updated May 16, 2026
One-click install
npx skills add https://github.com/honerlaw/agent-marketplace --skill ship-honerlaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/honerlaw/agent-marketplace/tree/main/plugins/minerva/skills/ship
Command: npx skills add https://github.com/honerlaw/agent-marketplace --skill ship-honerlaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns completed Minerva work into a ready-to-merge GitHub change by creating a branch and commit, opening a PR with proposal-derived context, and shepherding CI to a green result with a bounded auto-fix loop.

Core Features & Use Cases

  • Targeted work shipping: Ships a specific work unit by slug (or resolves the best match from Minerva context) and supports a bare mode when no work unit is found.
  • PR creation that reflects the work proposal: Builds a PR title and body from the active work unit’s proposal.md (otherwise uses git state in bare mode) and includes a clear summary and test-plan section.
  • CI watch with bounded remediation: Polls PR checks via ScheduleWakeup and applies targeted fixes up to three iterations, then either enables auto-merge or reports actionable failure state.
  • Idempotent behavior for repeated invocations: Detects an existing open PR for the branch and reuses it rather than failing or duplicating PRs.

Quick Start

Use the ship skill to publish your latest Minerva work unit as a PR and wait for checks by running: minerva:ship 005-add-payments

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate GitHub PR creation and CI checks for Minerva work?

To automate GitHub PR creation for Minerva work, this skill commits outstanding changes, pushes a branch, opens a PR with proposal-derived context, and shepherds CI to green using bounded automatic fixes.

What is the best way to ship a specific Minerva work unit by slug?

Shipping a specific Minerva work unit by slug requires passing the slug to the ship command, which resolves the correct worktree, commits the work, and opens a targeted GitHub pull request.

Do I need gh CLI authentication to open a PR and enable auto-merge?

Yes, gh CLI authentication is required to open a pull request, detect the default branch, poll PR checks, and enable the repo-supported auto-merge strategy only when checks are green.

How does CI watch handle failing checks with automatic fixes?

CI watch polls PR checks via ScheduleWakeup and applies targeted fixes up to three iterations, then either enables auto-merge if checks pass or reports an actionable failure state.

Can I reuse an existing open PR if I run the ship command multiple times?

Yes, the ship command is idempotent, detecting an existing open PR for the branch and reusing it rather than failing or duplicating pull requests on repeated invocations.

What happens when no Minerva work unit is found during the shipping process?

When no Minerva work unit is found, the process falls back to bare mode, using the existing git state alone to build the PR title, body, and commit instead of relying on proposal.md.