Run any Skill in Manus with one click

ship

Stars1

Forks0

UpdatedJune 11, 2026 at 23:16

Take a finished change from local diff to merged PR. Use whenever the user says "ship it", "/ship", "get this merged", or has a completed change ready to go out. Drives the change to a goal state through non-negotiable quality gates.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

leighstillard

leighstillard/ship-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ship
description	Take a finished change from local diff to merged PR. Use whenever the user says "ship it", "/ship", "get this merged", or has a completed change ready to go out. Drives the change to a goal state through non-negotiable quality gates.

Ship

Goal

The change is merged to the default branch, and every invariant below holds with evidence. You decide the path; the invariants are not yours to waive.

Invariants

These are preconditions, not steps. If any is unmet, achieving it becomes your next action.

Simplified before verified. A /simplify pass has run over the final shape of the diff. Code changes after simplify don't require re-simplifying unless substantial.
No PR exists without a VERIFIED verdict. /verify has ended in VERIFIED, with concrete evidence (commands + output, end-to-end execution). NOT VERIFIED, partial, or "tests pass" does not satisfy this. Any code change after a VERIFIED verdict invalidates it — re-run /verify before relying on it again.
No PR exists without a design verdict if the diff is user-visible. /design-check has passed or correctly declared itself not applicable.
The PR carries its evidence. Opened via /pr, with the verify evidence (and design screenshots, if any) in the body.
No merge without independent review addressed. /codex:review has run against the open PR and every finding is fixed, or rebutted with reasoning on the thread. Non-trivial fixes re-trigger invariant 2.
No merge while red or contested. CI green, review comments addressed, conflicts resolved — /babysit owns this until merge completes.

Operating rules

The natural path is 1→6, but reordering is yours when it serves the goal (e.g. a babysit CI fix loops you back through invariants 2 and 5 — do that without being told).
Report state transitions tersely: [ship] verify: VERIFIED → opening PR.
Maintain a checklist of invariant status (TodoList if available) so an interrupted session resumes correctly.
Escalate, don't waive: if an invariant can't be met without a decision above your pay grade (large refactor needed, broken main, disputed review, missing credentials), pause and ask the user. Declaring the goal met with an unmet invariant is the one prohibited move.

More from this repository

same repository

babysit

leighstillard/ship-skills

Shepherd an open PR to merge. Watches CI, fixes failures, addresses review comments, resolves merge conflicts, and enables auto-merge when green. Use after opening a PR, when the user says "babysit", "watch the PR", "get this merged", or as the final step of /ship.

2026-06-111

design-check

leighstillard/ship-skills

Visual and UX review pass for any change that touched UI — frontend components, HTML, CSS, templates, dashboards, CLI output formatting, or anything a human looks at. Use whenever a diff includes UI files, when the user asks for a design review, or as part of /ship. If the diff touched nothing user-visible, state that and exit immediately.

2026-06-111

leighstillard/ship-skills

Commit, push, and open a pull request for the current change. Use when the user says "open a PR", "ship this", "commit and push", or as the PR step of /ship. Handles branch hygiene, commit message quality, and PR description.

2026-06-111

verify

leighstillard/ship-skills

Prove a change actually works before it ships. Use whenever a change is "done" and needs validation — after implementing a feature, fixing a bug, or before opening a PR. Also trigger when the user says "verify", "check this works", "is this actually working", or invokes /ship. Tests passing is not sufficient evidence; this skill drives the change end-to-end.

2026-06-111

name	ship
description	Take a finished change from local diff to merged PR. Use whenever the user says "ship it", "/ship", "get this merged", or has a completed change ready to go out. Drives the change to a goal state through non-negotiable quality gates.

Ship

Goal

The change is merged to the default branch, and every invariant below holds with evidence. You decide the path; the invariants are not yours to waive.

Invariants

These are preconditions, not steps. If any is unmet, achieving it becomes your next action.

Simplified before verified. A /simplify pass has run over the final shape of the diff. Code changes after simplify don't require re-simplifying unless substantial.
No PR exists without a VERIFIED verdict. /verify has ended in VERIFIED, with concrete evidence (commands + output, end-to-end execution). NOT VERIFIED, partial, or "tests pass" does not satisfy this. Any code change after a VERIFIED verdict invalidates it — re-run /verify before relying on it again.
No PR exists without a design verdict if the diff is user-visible. /design-check has passed or correctly declared itself not applicable.
The PR carries its evidence. Opened via /pr, with the verify evidence (and design screenshots, if any) in the body.
No merge without independent review addressed. /codex:review has run against the open PR and every finding is fixed, or rebutted with reasoning on the thread. Non-trivial fixes re-trigger invariant 2.
No merge while red or contested. CI green, review comments addressed, conflicts resolved — /babysit owns this until merge completes.

Operating rules

The natural path is 1→6, but reordering is yours when it serves the goal (e.g. a babysit CI fix loops you back through invariants 2 and 5 — do that without being told).
Report state transitions tersely: [ship] verify: VERIFIED → opening PR.
Maintain a checklist of invariant status (TodoList if available) so an interrupted session resumes correctly.
Escalate, don't waive: if an invariant can't be met without a decision above your pay grade (large refactor needed, broken main, disputed review, missing credentials), pause and ask the user. Declaring the goal met with an unmet invariant is the one prohibited move.