🚀
DevOpsPython

Ship

by evo-hq

Ship is a DevOps skill for Claude Code, published by evo-hq in evo.

1.4K stars105 forkson evo-hq/evoAdded 2026/08/19+1% in starsRepository updated 2026/07/17
agent-skillsautonomous-agentsautoresearchclaude-codecode-optimizationcodexevolutionary-algorithmsllm-agents
Install in seconds
Install Ship
Copy Ship into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/evo-hq/evo/tree/main/plugins/evo/skills/ship ~/.claude/skills/ship

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/evo-hq/evo.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
plugins/evo/skills/ship/SKILL.md in evo-hq/evo
Installs to
~/.claude/skills/ship
Collection
One of 8 skills cataloged from this repository
Category
DevOps798 skills

What Ship does

Ship turns a finished evo run into a clean, mergeable change by distilling the best-scoring experiment down to its minimal diff, restoring test integrity, and opening a pull request or merging locally. Use when asked to land, merge, ship, or turn a finished optimization into a reviewable change.

Ship is cataloged under DevOps on DirSkills. Ship comes from a repository tagged agent-skills, autonomous-agents, autoresearch, claude-code and code-optimization.

Documentation

README

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

/evo:ship            # ship the auto-selected winner
/evo:ship exp_0042   # ship a specific experiment instead

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Ship

  • What else does evo-hq publish alongside Ship?

    Ship is one of 8 skills that DirSkills catalogs from evo-hq/evo, the repository it ships in. Its siblings there include Discover, Evo Report and Evo Subagent Protocol. Each one is a separate skill with its own page in this directory, installs the same way Ship does, and is maintained by evo-hq in that same repository. The rest of the collection is listed on the evo-hq/evo page.

  • How does Ship compare to other DevOps skills?

    Ship ranks #365 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Ship against them. Open each page to compare what they document and how they install.

More from evo-hq/evo

Ship is one of 8 skills cataloged on DirSkills from evo-hq/evo.

See all 8 skills
🔍
2w ago

Discover

Discover initializes an evo workspace for the current repository by exploring the codebase, proposing optimization dimensions, constructing a benchmark, and running a baseline experiment. Use it when starting a new evo run or instrumenting a project for autonomous optimization.
AI Engineering
1.4K105
📊
2w ago

Evo Report

Evo Report provides read-only reports from recorded evo workspace state, including score charts, frontier candidates, and status summaries. Use it when someone asks what happened overnight, what improved, or wants a quick chart without opening the dashboard.
Data
1.4K105
🤖
2w ago

Evo Subagent Protocol

Evo Subagent Protocol defines the brief shape and execution loop that evo optimization subagents follow when dispatched from /optimize. Orchestrators use it to write valid briefs and debug subagent behavior; subagents use it to drive required verifier checks and read-edit-run iteration.
AI Engineering
1.4K105
🎯
2w ago

Finetuning

Finetuning selects or diagnoses a training move—SFT, LoRA, DPO/KTO/ORPO, RFT, GRPO/PPO/RLOO, RLHF—based on reward shape and literature, then gates runs with smoke tests, early stopping, and diagnostics. Use it when fine-tuning, post-training, reward design, or weight updates come up.
AI Engineering
1.4K105
⚙️
2w ago

Infra Setup

Infra Setup guides switching the evo backend between local worktrees, pool slots, and remote providers like Modal, E2B, or SSH. It checks prerequisites, verifies auth, and shows the exact config commands so experiments run on the intended infrastructure.
DevOps
1.4K105
🧪
2w ago

Optimize

Optimize drives structured autoresearch iteration after evo:discover and the baseline commit, orchestrating subagents to run experiments and improve the current best frontier. Use it when the user invokes /evo:optimize or asks to try ideas, variants, or continue an evo search.
AI Engineering
1.4K105