ship-change
Skill1 starsChanged 2 months agoMITView on GitHub
The development loop for a change that fits in roughly one session — orient if needed, pick the domain skill for the area, build test-first, deslopify, clean the commits, self-review, security-check if warranted, ship. Use when asked to "fix X", "add Y", "change Z" and it's a bounded change, not a multi-session feature (that's new-feature).
5 other projects use a version of this.
Adopted by
Most recently taken up by
- mralexivy/AutoModetheir own version, first seen Nov 8, 2026
- davidscotttufts/hyvemindtheir own version, first seen Nov 1, 2026
- fnayou/dotfilestheir own version, first seen Oct 25, 2026
- LandonTomaine/LT-Agentstheir own version, first seen Oct 20, 2026
- YangFan-Code-Star/context-devtheir own version, first seen Aug 18, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- mralexivy/AutoMode★ 8same name
- fnayou/dotfiles★ 2same name
- YangFan-Code-Star/context-dev★ 2same name
- davidscotttufts/hyvemind★ 0same name
- LandonTomaine/LT-Agents★ 0same 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 repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bigquery-analyticsSkill
- cache-invalidationSkill
- mongo-aggregationSkill
- mongo-modelingSkill
- postgres-aggregationSkill
- postgres-indexingSkill
- redis-coordinationSkill
- redis-patternsSkill
- review-querySkill
- code-migrationSkill
- cut-releaseSkill
- data-migrationSkill
- deploy-serviceSkill
- hotfixSkill
- rollbackSkill
- design-endpointSkill
- design-eventSkill
- design-schemaSkill
- evolve-contractSkill
- scaffold-nestjs-moduleSkill
- scaffold-projectSkill
- incident-responseSkill
- investigate-bugSkill
- on-callSkill
- postmortemSkill
- audit-skillsSkill
- distill-review-styleSkill
- write-skillSkill
- debug-with-tracesSkill
- define-alertsSkill
- instrument-serviceSkill
- evaluate-dependencySkill
- grillSkill
- handoffSkill
- orientSkill
- phased-deliverySkill
- spikeSkill
- to-questionnaireSkill
- write-adrSkill
- write-prdSkill
- devops-pr-reviewSkill
- go-backend-pr-reviewSkill
- nestjs-backend-pr-reviewSkill
- python-backend-pr-reviewSkill
- react-frontend-pr-reviewSkill
- bisectSkill
- break-couplingSkill
- dead-code-sweepSkill
- deslopifySkill
- extract-moduleSkill
- rebase-cleanSkill
- resolve-merge-conflictsSkill
- split-commitSkill
- tddSkill
- wait-whatSkill
- wide-renameSkill
- bullmqSkill
- kafkaSkill
- sqs-consumerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
If mid-change you discover it's actually a multi-session job → stop, switch to workflows/new-feature.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow — ship a change
Orchestrator for the common case: a bounded change, one session. Invoke each named skill with the Skill tool.
Loop
| # | Invoke | When |
| 1 | planning/orient | first time working in this repo — skip if you know it |
| 2 | the domain skill for what you're touching: | |
design/evolve-contract | changing an existing API / response / enum / event | |
data/review-query · data/postgres-indexing · data/mongo-modeling · data/redis-patterns | the change is a query / schema / cache path | |
queues/sqs-consumer · queues/kafka · queues/bullmq | the change is a producer / consumer | |
observability/instrument-service | adding a service surface that needs visibility | |
| 3 | quality/tdd | build it — failing test first, minimum to pass |
| 4 | quality/deslopify | before committing — remove restating comments, impossible-case guards, etc. |
| 5 | quality/split-commit | one logical change per conventional commit |
| 6 | pr-review/<stack> | review your own diff as if it were someone else's |
| 7 | security/security-review | only if the change touches auth, user input, file handling, external requests, or dependencies |
| 8 | deployment/deploy-service | if you're the one shipping it |
Rules
- Step 2 is "load the reference for the area you're in" — often just one skill.
- Steps 4–6 are non-negotiable on any change that touched code.
- Step 7 is conditional — don't run a full security pass on a copy tweak.
- If mid-change you discover it's actually a multi-session job → stop, switch to
workflows/new-feature.
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.