aube-bump
Installation
SKILL.md
Bumping vendored aube to a new upstream
Mental model
vendor/aube/** is plain tracked files in nub's history — no submodule, no pin. An aube change is an ordinary nub PR touching vendor/aube/**. Everything lives in the nub repo; you do not need a clone of nubjs/aube and you do not touch the nub-fork branch.
| Thing | Where |
|---|---|
| Source of truth | vendor/aube/** on nub main |
| Upstream | jdx/aube, as the aube-upstream remote |
| The base we're on | vendor/aube/UPSTREAM (commit + tag) |
| Merge venue | built on demand, thrown away |
The venue is derived, not stored. A 3-way merge needs a commit whose tree is the vendored state and whose ancestry contains the upstream base — both already in nub's object store. Deriving it at bump time means it cannot drift, and rerere's cache lives in nub and persists across bumps.
The core: two machine-generated conflict lists
You never hand-review the upstream diff.