How do I install the Format Bump skill?

Run npx skillmds@latest add oxidecomputer/format-bump in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Format Bump safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Format Bump?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Format Bump free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Format Bump?

oxidecomputer (@oxidecomputer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Format Bump by oxidecomputer — Agent Skill

Name: Format Bump
Author: oxidecomputer

Format Bump

The FORMAT_VERSION bump loop — regenerate the checked-in binary bundle fixtures on a capture host and fold them into the schema commit so main is never red. Use when bumping FORMAT_VERSION (new DisplayNode kind, Bytes notation, any bundle schema/io change) or when hansei-runtime fixture tests fail to load bundles after a schema change.

File contents

Format bumps

A FORMAT_VERSION bump (in hansei-bundle/src/io.rs) invalidates the checked-in binary fixtures in hansei-runtime/tests/fixtures/*.tinfo — cargo nextest run -p hansei-runtime fails to load them until they are regenerated with test-programs/capture-snapshots.sh. That script needs gcore, so it runs on an illumos or Linux host, not macOS.

Never weigh the bump itself in a design trade-off — bumping is routine and free; this loop is its only cost.

The loop

Ordering matters: the capture host builds the commit at HEAD, and main must never be left with a red hansei-runtime.

Land the schema change locally: everything green (cargo nextest run --no-fail-fast — the fixture-loading tests in hansei-runtime are the expected reds until step 3), commit.
Push, and sync the capture host to that commit.
Regenerate on the capture host: run test-programs/capture-snapshots.sh, then copy the regenerated hansei-runtime/tests/fixtures/*.tinfo back.
Fold the fixtures into the same commit: git commit --amend, then force-push — the standing convention for fixture fixes verified on another host.
Prove it: cargo nextest run -p hansei-runtime locally, then the full suite on every platform (which tests what is pushed, so re-push first after amending).

Which host captures, how to reach it, and where to push are per-checkout facts — see the untracked CLAUDE.local.md.

Notes

The fixtures' recorded line numbers go quietly stale if the fixture programs changed too (they are not rebuilt from source by any test) — this loop is also how they are refreshed after a test-programs reflow.

---name: format-bumpdescription: The FORMAT_VERSION bump loop — regenerate the checked-in binary bundle fixtures on a capture host and fold them into the schema commit so main is never red. Use when bumping FORMAT_VERSION (new DisplayNode kind, Bytes notation, any bundle schema/io change) or when hansei-runtime fixture tests fail to load bundles after a schema change.---# Format bumpsA `FORMAT_VERSION` bump (in `hansei-bundle/src/io.rs`) invalidates thechecked-in binary fixtures in `hansei-runtime/tests/fixtures/*.tinfo` —`cargo nextest run -p hansei-runtime` fails to *load* them until they areregenerated with `test-programs/capture-snapshots.sh`. That script needs`gcore`, so it runs on an illumos or Linux host, **not macOS**.Never weigh the bump itself in a design trade-off — bumping is routine andfree; this loop is its only cost.## The loopOrdering matters: the capture host builds the commit at `HEAD`, and`main` must never be left with a red `hansei-runtime`.1. Land the schema change locally: everything green (`cargo nextest run --no-fail-fast` — the fixture-loading tests in `hansei-runtime` are the expected reds until step 3), commit.2. Push, and sync the capture host to that commit.3. Regenerate on the capture host: run `test-programs/capture-snapshots.sh`, then copy the regenerated `hansei-runtime/tests/fixtures/*.tinfo` back.4. Fold the fixtures into the *same* commit: `git commit --amend`, then force-push — the standing convention for fixture fixes verified on another host.5. Prove it: `cargo nextest run -p hansei-runtime` locally, then the full suite on every platform (which tests what is pushed, so re-push first after amending).Which host captures, how to reach it, and where to push are per-checkoutfacts — see the untracked `CLAUDE.local.md`.## Notes- The fixtures' recorded line numbers go quietly stale if the fixture *programs* changed too (they are not rebuilt from source by any test) — this loop is also how they are refreshed after a `test-programs` reflow.

Frequently asked questions