Menu
Use when publishing crates to crates.io, bumping versions, and managing the release pipeline. Load during the Deployment phase of SDLC.
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 designing module placement, type design, and API surface for new features in rvlibs. Load during the Design phase of SDLC.
Use when refactoring large files (800+ lines) — both source and test code — by splitting into sibling modules or submodules based on scope and concern boundaries.
Use when reviewing code changes for correctness, style, conventions, testing, and security. Load during Implementation phase as a quality gate.
Use when implementing new features in rvlibs following conventions and existing patterns. Load during the Implementation phase of SDLC.
Use when triaging, diagnosing, and registering bugs or issues. Covers classification, reproduction, severity, and registration.
Use when ensuring feature quality through testing, coverage gates, and pre-merge verification. Load during the Testing phase of SDLC.
| name | release-management |
| description | Use when publishing crates to crates.io, bumping versions, and managing the release pipeline. Load during the Deployment phase of SDLC. |
SDLC Phase: Deployment
Release crates to crates.io, bump versions, and manage the release pipeline.
| Change Type | Version Component | Example |
|---|---|---|
| Breaking API change | MAJOR | 1.2.3 → 2.0.0 |
| New feature (backward-compatible) | MINOR | 1.2.3 → 1.3.0 |
| Bug fix (backward-compatible) | PATCH | 1.2.3 → 1.2.4 |
Breaking changes include: removing a public item, changing a function signature, adding a required trait bound, altering enum variant shape.
cargo test --workspacecargo clippy --all-targets --all-features -- -D warningscargo doc --no-depsCargo.toml per the rules abovecargo publish --dry-run succeeds (catches missing fields, license issues, etc.)The publish order follows the dependency graph. Foundation crates with no internal dependencies publish first; leaf crates that depend on others publish last.
Typical order for rvlibs:
rvlibs — Shared contracts, zero dependenciesrvmath — Depends on rvlibs onlyrvtest-macros — Depends on rvlibs onlyrvtest — Depends on rvlibs, optionally on rvtest-macrosrvnx — Depends on rvlibs, rvmathrvfx — Depends on rvnxPath dependencies must be switched to version dependencies before publishing. Verify that each crate's Cargo.toml uses the correct version spec for workspace-internal dependencies.
git tag v{version}git push origin v{version}