ship
Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.
npx skills add evo-hq/evo --skill ship --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Ship Turn a finished evo run into a change a maintainer would merge. The optimize loop leaves a tree of committed experiments. The winning worktree diff is not mergeable as-is: it carries debug prints, search-process churn, over-broad edits, and sometimes a test that was relaxed to clear a gate. Shipping is the step that re-derives the *minimal clean change* reproducing the winning behaviour, lands it the way the repo expects (PR or merge), and reports how mergeable it is. Correctness is the floor, not the goal. The score says the behaviour works; this skill decides whether the *diff* is fit to merge. ## Invocation ```bash /evo:ship # ship the auto-selected winner /evo:ship exp_0042 # ship a specific experiment instead ``` ## Stage 1 -- Select the winner Pick the experiment to ship, then confirm it with the user before touching their tree. ```bash evo status # current best valid score + counts evo report # top valid experiments table + score chart ``` - The default winner is the highest-scoring valid result in the graph history, not the frontier. `evo frontier` is for choosing where to branch next; it can exclude an exhausted branch whose score is still the right thing to ship. A
- Invocation
- Stage 1 -- Select the winner
- Stage 2 -- Distill to a mergeable change
- Stage 3 -- Land
- Stage 4 -- Mergeability report (advisory)
- Guardrails (firm)
evo status # current best valid score + counts evo report # top valid experiments table + score chart evo diff <root_id> <winner_id> # target-scoped cumulative diff, baseline -> winner evo run <winner_id> --check # or the project's benchmark / test command git remote -v
What does the ship skill do?
Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.
How do I install it?
Run `npx skills add evo-hq/evo --skill ship --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evo-hq/evo, a repository with 1,359 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
