Menu
Roll a kit release out to one adopter repo — download, sha256 three-way, banked rollback, carve-out scan, born-red PR, tree-verified merge.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Cut + publish a substrate-kit release — version bump PR, workflow_dispatch publish, three-way asset verification, adopter distribution wave.
Land the session — claim, born-red card first, READY PR, batched work, close-out docs, flip complete last; land on green.
Resolve every reference in the ask before acting — inventory, resolve or search each one, report unfindables explicitly, state the assembled picture back (Q-0273 seed skill).
Hand the owner finished steps, not directions — deep links, paste-ready blobs, his path walked once, one batched sitting, payoff + verification stated (Q-0273 seed skill).
The checkpoint at natural pauses — should this action also be executed? does this lesson deserve a permanent home shippable NOW? Route via the table (Q-0273).
Turn a fragmented owner ask into main ideas, a restated fuller picture, a skill-index map, and structured-choice owner questions — before building (understand-and-reflect, executable).
| name | upgrade-distribution |
| description | Roll a kit release out to one adopter repo — download, sha256 three-way, banked rollback, carve-out scan, born-red PR, tree-verified merge. |
Roll a substrate-kit release out to venture-lab — one target repo of the distribution wave. Playbook-grade wave runbook (grounded-skills plan §7.2).
Moves the target's vendored bootstrap.py to the released version with the
sha256 three-way proof, the banked rollback path, a carve-out scan for local
modifications, and a born-red PR — then verifies MERGED MAIN against the
tree, never a registry line or a PR read.
git fetch origin main && git reset --hard origin/main. A stale clone
reads stale orders and re-executes finished work.gh release download vX.Y.Z --repo menno420/substrate-kit --pattern 'bootstrap.py*' --pattern 'release.json'
then move the downloaded dist to bootstrap.py.new (the consumer flow
release.json names).sha256sum bootstrap.py.new
must equal BOTH the sha256 field in release.json AND the kit repo's
committed dist/bootstrap.py at the release's bump SHA. Any mismatch:
stop and report; do not upgrade..sessions/ card declaring
in-progress as the first commit on the wave branch; open the PR READY;
land it on green — merge directly or via the enabler (the session-close
rails apply verbatim).python3 bootstrap.py.new upgrade. It banks the OLD dist to
.substrate/backup/ (verify the banked bootstrap-<old-version>.py
exists — that is the rollback path) and consumes its own inputs..substrate/upgrade-report.md: consumer-edited
and diverged docs are LOCAL MODIFICATIONS the upgrade must not
clobber; list them verbatim in the PR body. template-improved applies
only under --apply-docs and only to consumer-untouched docs.python3 bootstrap.py check --strict and
python3 bootstrap.py check --strict green (own card's designed hold
excepted); flip the card complete, delete the claim, push.git fetch origin main && git log -1 --oneline origin/main and read the
vendored dist's version header at origin/main. Never trust an MCP PR
read alone for merge/CI state (~25-min-stale data) — cross-check the
tree or the Actions runs.<repo>: vOLD → vNEW · sha256 3-way ✔ · bank ✔ · carve-outs: <n or none> · PR #<n> merged @ <sha> · tree-verified ✔
Known failure modes + fixes:
do-not-automerge label applied seconds after MCP PR-create misses the
opened-event label snapshot and reds the first CI round — cure with one
empty commit (git commit --allow-empty) to re-fire the enabler.Declared capabilities: edit (the vendored dist + docs), run (git + gh + the checks).