Rust release

Skill nyquistwilder/personal-pi/skills/rust-release

Rust release workflow for version bumps, changelogs, tags, cargo package, crates.io publishing, release-plz, cargo-dist, checksums, binaries, SBOMs, safeguards, and post-release verification.From its SKILL.md

Install

npx -y skills add nyquistwilder/personal-pi --skill rust-release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 349 tokens by cl100k_base, as published. Nobody here has run it

Rust Release

Rule

Validate before publishing and require explicit approval for irreversible operations.

Hard Stops

Stop before:

Tagging, publishing to crates.io, pushing release pages, signing artifacts, uploading binaries, publishing containers, or using credentials.
Releasing from a dirty tree or with failing validation unless explicitly approved.
Adding release-plz, cargo-dist, signing, SBOM, or provenance automation without approval.
Publishing public crates without checking SemVer and package contents.

Defaults

Run full validation, inspect cargo package, and keep generated artifacts out of git.
Use cargo semver-checks for public library crates when configured or before publishing.
Use release-plz for crate release PRs/changelogs/version bumps when approved.
Use cargo-dist for binary distribution when cross-platform installers/artifacts are needed and approved.
Generate checksums for binary artifacts; add signing/SBOM/provenance only when policy requires it.
Start new automation with dry runs.

Workflow

Inspect version policy, changelog, git state, CI, crate metadata, features, and release targets.
Confirm target version and publish targets.
Run just check, package/build/doc checks, semver checks when relevant, and cargo package --list.
Build artifacts in ignored directories and inspect contents.
Ask before tagging, publishing, signing, or uploading.
Verify published crates or artifacts when approved.

Completion

Report target version, files changed, artifacts, package checks, tag/publish actions performed or skipped, and verification results.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 349 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

validate before publishing
require explicit approval for irreversible operations
inspect cargo package output
keep generated artifacts out of git
run cargo semver checks for public libraries
start new automation with dry runs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.