Automates version bumping, pre-flight checks, and release tagging for the czsc Rust-Python hybrid package.
npx skills add https://github.com/waditu/czsc --skill czsc-release
Please help me install this Agent Skill. Skill: czsc-release Source: https://github.com/waditu/czsc/tree/main/.claude/skills/czsc-release Command: npx skills add https://github.com/waditu/czsc --skill czsc-release
Releasing the czsc library is error-prone because it is a Rust + Python hybrid package (PyO3 + maturin) that must publish synchronized versions to both crates.io and PyPI, and past releases suffered repeated re-releases due to skipped pre-flight checks. This Skill enforces a disciplined, checklist-driven release workflow with mandatory human authorization before irreversible actions like pushing tags.
Ask the assistant to release czsc by saying "bump czsc to the next rc version and prepare the release", then confirm each gated step as prompted.
High-intent search queries and answers about installing and using this skill.
Use a workflow that keeps a single version source in the workspace Cargo.toml, runs cargo fmt/clippy/test plus pytest pre-flight checks, bumps the CHANGELOG, then pushes a v-prefixed tag to trigger CI publishing to PyPI and crates.io. Always confirm before pushing tags since PyPI version names cannot be reused.
It reads the current version from Cargo.toml [workspace.package].version and inspects the CHANGELOG [Unreleased] section. Breaking changes bump the major version, additions bump the minor, fixes bump the patch, and published rc versions require incrementing the rc number.
No. Once a version number is uploaded to PyPI it is permanently occupied and cannot be reused or force-pushed. If a release fails after the tag was pushed, you must bump to the next patch or rc number and re-release with the fix included.
Cargo publish fails if you only update [workspace.package].version but forget the version fields of path dependencies in [workspace.dependencies]. All internal crate version references must be updated together so the published crates resolve consistently.
The checks include cargo fmt, clippy with all targets, cargo test, maturin develop rebuild, stub generation drift verification via git diff, pytest unit and slow tests, and ruff lint and format checks. Any failure stops the release before version bumping.
No. Pushing tags triggers CI that uploads to PyPI and is irreversible, so the skill always pauses and asks for explicit user authorization before running git tag, git push origin master, or git push of the version tag.
andreciniGenerate a new CHANGELOG.md release entry from merged pull requests and commits.
rust-worksAutomate Rust project releases with version bumps, changelog updates, and publishing.
castoriniAutomate PyPI release workflows for Castorini projects with version bumps and publishing.
jmagarCoordinate Rust release workflows with release-plz, cargo-dist, and cocogitto.
