Ship
Skill honerlaw/agent-marketplace/plugins/minerva/skills/ship
A personal plugin marketplace for AI coding agents. Each plugin provides skills and automation scripts.
npx -y skills add honerlaw/agent-marketplace --skill shipAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Ships the current work — commits outstanding changes to a branch, opens a pull request, watches CI via non-blocking ScheduleWakeup polling, fixes CI failures, and enables auto-merge. Use when the user asks to ship, push, open a PR for, or merge the current work — closing the minerva lifecycle after `minerva:work` / `minerva:promote` / `minerva:review` — or when they invoke `minerva:ship`.
SKILL.md
3.2 KB, 689 tokens by cl100k_base, as published. Nobody here has run it
Close the minerva lifecycle by committing outstanding work to a branch, opening a PR titled and described from the active work unit's proposal.md, watching CI to green with a bounded auto-fix loop (3 iterations) via ScheduleWakeup polling, and enabling auto-merge when repo permissions allow.
Usage
minerva:ship— ships the work unit inferred from current-session context, or the most-recently-modified if context is ambiguous, or runs in bare mode if no work unit is foundminerva:ship 005-add-payments— ship the named unit explicitly
Pre-flight checks
Bail with a clear, one-line message on any failure:
- Git repo.
git rev-parse --is-inside-work-treereturns true. ghCLI available and authenticated.gh auth statusexits 0.- Something to ship. At least one of:
git status --porcelainis non-empty (staged, unstaged, or untracked changes), or- the current branch has commits ahead of the default branch.
- Not a no-op. If currently on the default branch with zero commits ahead and no local changes, there is nothing to ship — stop.
Protocol
The full step protocols live verbatim in references/protocol.md — read it now, before executing: Target resolution → Worktree addressing → Default-branch detection → Branch creation → Commit outstanding changes (Hard gate #1: commit message confirmation) → Push & open PR (Hard gate #2: PR title + body confirmation) → CI watch & auto-fix loop (ScheduleWakeup polling at delaySeconds: 270, bounded 3-iteration auto-fix) → Auto-merge → Final report, plus Lifecycle nudges and Worktree handling.
Idempotency
Ship does not write its own metadata file or append a ## Shipped marker to scratchpad.md. The PR URL lives on GitHub; nothing minerva-side needs to remember it. Re-running on a branch that already has an open PR will detect that (gh pr view) and pick up at the CI-watch step instead of re-creating.
Wake-ups re-invoke minerva:ship; the skill detects the existing PR and resumes the watch loop using the iteration count carried in the wake-up prompt.
Out of scope
- Writing to
.minerva/knowledge/directly. All durable knowledge goes throughminerva:promote. - Running
minerva:promoteorminerva:reviewautomatically. Only nudges, never auto-invokes — keeps the user in control of what gets promoted and reviewed. - Worktree cleanup. Owned by
minerva:cleanup. - A strict mode that turns nudges into hard blockers. Deferred; users who want strict ordering can run the skills in order themselves.
- Replacing
ship-itfor non-minerva projects. This skill assumes a.minerva/project or runs in explicit bare mode; the genericship-itskill is still the right tool when the user is not in a minerva project.
What ships with it: 1 file
14.2 KB alongside SKILL.md
references/
- protocol.md14.2 KB