ship-small
Skill2 starsChanged 16 days agoMITView on GitHub
Ship a small, low-risk change (a copy or docs fix, a small web UI tweak) from intent to a validated pull request with one command per stage, safe for a small model (Haiku). Use for typos, wording, doc fixes, link fixes and small component or style tweaks; anything else escalates by itself.
- Commits and pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- kaelen2026/skillstheir own version, first seen Oct 13, 2026
- torisKR/toris-agenttheir own version, first seen Jul 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- torisKR/toris-agent★ 2same name
- kaelen2026/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/CLAUDE.mdCLAUDE.md
- starter/CLAUDE.mdCLAUDE.md
- template/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- add-moduleSkill
- add-operationSkill
- codifySkill
- raise-the-barSkill
- releaseSkill
- reviewSkill
- scaffold-pluginSkill
- self-auditSkill
- write-adrSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
3 STOP: this is a correct outcome, not an error.
- Very specific: line 33
Never write a name of a person, employer, customer or private repository into a file.
- Very specific: line 35
If the change turns out bigger than the job you were given, run S escalate "one sentence why" and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ship a small change
A script decides what is small and what is not; you never judge. Run the stages in order. Every command prints one
JSON line; do what its next field says, literally. S below is the uv run --script .../scripts/ship.py prefix that
next prints; always cd into your worktree first (your shell forgets it between commands).
| Stage | Command | Does |
| 1 | S start SLUG | New worktree and branch (SLUG: 3-41 chars, lowercase, digits, dashes) |
| 2 | S classify --files PATH... | Before editing: is this file allowed? Exit 0 = edit it, exit 3 = not allowed |
| 3 | edit the files | Smallest edit that does the job. No new or deleted files |
| 4 | S classify | Reads your real diff: lane low or STOP |
| 5 | S check | Checks for exactly your files; fixes whitespace and formatting itself |
| 6 | S pr "type(scope): summary" --body "why" | Commits, pushes, opens the PR labelled risk: low, auto-merge off |
| 7 | S wait | Waits for CI; add --budget 540 and a 600000 ms shell timeout to wait longer |
| 8 | S merge PR | Merges your pull request once CI OK is green at its exact head; it re-checks the diff itself and refuses anything not small |
| 9 | S verify | After the merge: Docs run green and the live page shows your text |
S <stage> --help prints a stage's usage, an example and the exit codes. Exit codes: 0 go on with next. 1 this stage failed: fix exactly what detail names, then repeat the stage.
3 STOP: this is a correct outcome, not an error. Send the JSON line to whoever started you and run nothing else. 4 still running: run the same command
again. 2 you used the command wrongly: read msg.
Rules that no command can enforce:
- The second failure of any stage stops the change by itself (exit 3). Never retry a third time, never work around.
- Merge only with
S merge, never touch auto-merge, never rungit push,git commit,gh pr mergeormake pryourself, never use--no-verify. The stages do all of it; a pull request that is not small is the orchestrator's. - Never write a name of a person, employer, customer or private repository into a file. If
checkreports a confidential term, reword the text and never repeat the term anywhere. - If the change turns out bigger than the job you were given, run
S escalate "one sentence why"and stop.
The rules (paths, diff checks, limits) live in scripts/ship.py; background in docs/SHIP_SMALL.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

