Menu
Cut a Curio release — version bump, changelog, tag, artifacts. Use when asked to release, tag, or publish a version.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Add a new content-source module to curio-core (a feed format, a site-specific layout, or a post-v1 enrichment provider). Use when a task asks Curio to understand a new kind of source.
Change or extend a published Curio contract (curio.frontmatter.v1, curio.events.v1, curio.manifest.v1) without breaking consumers. Use whenever a task touches frontmatter keys, event envelope/types, manifest shape, or anything under schemas/.
| name | release |
| description | Cut a Curio release — version bump, changelog, tag, artifacts. Use when asked to release, tag, or publish a version. |
Pre-1.0 status: the full release pipeline (draft GitHub releases, 3-OS
matrix, SHA256SUMS + minisign + SBOM) lands in Phase 1 of
docs/design/roadmap.md. Until it exists, a release is exactly this:
just ci locally AND CI green on main. No
release from a red or dirty tree.[workspace.package] version
in the root Cargo.toml (crates inherit it). Bump it in its own commit:
chore(release): v0.X.Y. Follow semver; while pre-1.0, breaking changes
bump the minor.schemas/ changed since the last tag, verify
schemas/CHANGELOG.md records it and no vN file was edited in place
(git diff <last-tag> -- schemas/).vX.Y.Z on the release commit. Human pushes tags
— agents never push.