Menu
Use when preparing a new crate release, bumping versions, or tagging a release
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
Use when the user wants to create a new cryochamber application, set up a scheduled agent task, or scaffold a cryo project with plan.md and cryo.toml
Use when the user wants a screenshot of the cryohub web dashboard for documentation, README, mdbook, or a slide deck. Spawns cryohub on a chamber workspace, drives headless Chrome, and saves a PNG to the requested path.
Use when the user wants visual state machines of the cryochamber daemon — the overall event loop around inbox messages and TODO-triggered wakes, plus per-item lifecycles for a message and for a reminder — rendered as hand-written SVGs
Use when a PR has review comments to address, CI failures to fix, or codecov coverage gaps to resolve
Use after implementing a feature or any code change to verify completeness and correctness before committing
| name | release |
| description | Use when preparing a new crate release, bumping versions, or tagging a release |
Guide for creating a new release of cryochamber.
Compare against the last release tag:
git tag -l 'v0.*' | sort -V # find latest tag
git log <last-tag>..HEAD --oneline # review commits
git diff <last-tag>..HEAD --stat # review scope
Apply semver for 0.x (pre-1.0):
make check
make check runs fmt-check + clippy + test in sequence. All must pass with zero warnings before proceeding.
Also confirm:
git status is cleanmain branch, up to date with originmake release V=x.y.z
This target bumps version in Cargo.toml, runs cargo check, commits as release: vX.Y.Z, tags vX.Y.Z, and pushes main plus tags. CI publishes the crate to crates.io.