菜单
Perform pull requests, merge branches, and Rust crate releases using cargo-smart-release. Use when releasing crates, creating PRs for release branches, merging release branches, or when the user asks for release workflow, dry-run release, changelog updates, or crate publishing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validates animation durations, enforces typography scale, checks component accessibility, and prevents layout anti-patterns in Tailwind CSS projects. Use when building UI components, reviewing CSS utilities, or enforcing design consistency.
Making changes to the app's functionality.
Create Criterion benchmarks with proper group macros and configuration. Use when writing benchmarks, creating benchmark groups, using criterion_group! and criterion_main! macros, setting throughput, or benchmarking multiple implementations. Handles benchmark groups, throughput metrics, conditional compilation, and proper black_box usage.
Read and parse GitHub issues; extract title, body, labels, checklists, and acceptance criteria to support triage and delegation.
Apply cognitive and perception-based UI principles from Laws of UX. Use when evaluating layout, interaction design, target size and distance, choice count, information grouping, memory load, or response time. Cites specific laws (e.g. Fitts's Law, Hick's Law) to justify design decisions or suggest improvements.
Work with async/await, futures, and asynchronous Rust code. Use when writing async functions, working with tokio or async-std, understanding futures, or implementing async traits. Handles async/await syntax, futures, executors, pinning, Send/Sync bounds, and async patterns.
| name | rust-release-workflow |
| description | Perform pull requests, merge branches, and Rust crate releases using cargo-smart-release. Use when releasing crates, creating PRs for release branches, merging release branches, or when the user asks for release workflow, dry-run release, changelog updates, or crate publishing. |
Guidelines for PRs, branch merges, and crate releases with cargo-smart-release.
cargo install cargo-smart-releaseorigin remoteRun a dry-run before any release. Default behavior is simulation only; no --execute means no changes.
# Basic dry-run for one or more crates
cargo smart-release <crate-name> [<crate-name> ...] [--update-crates-index]
# Thorough simulation (includes cargo publish dry-run; may have false positives)
cargo smart-release <crate-name> --dry-run-cargo-publish [--update-crates-index]
If package.metadata.scripts defines dry-release, use it:
cargo run -p <package-name> dry-release
After dry-run, cargo-smart-release may have modified changelogs. Update scaffolding and edit by hand:
cargo changelog --write <crate-name>
Then manually:
<csr-read-only-do-not-edit/> and <csr-id-...> sections are intact if you want cargo-smart-release to manage themAfter changelog polish, update READMEs:
flow-fcs = "0.2.0")Only after dry-run and manual review:
cargo smart-release <crate-name> [<crate-name> ...] --update-crates-index --execute
Or use the project's publish script if defined.
cargo-smart-release creates annotated tags (<crate-name>-v<version>) and pushes them with the release. If the release fails partway (e.g. cargo publish fails for auth), tags for later crates may be missing.
Verify tags exist for each released crate:
git tag -l '<crate-name>-v*'
Create missing tags if the release completed for a crate but the tag was not created:
git tag -a <crate-name>-v<version> <release-commit> -m "Release <crate-name> v<version>"
git push origin <crate-name>-v<version>
main (or target branch)cargo smart-release ... --execute from the merged branch (or use automation)For crates below 1.0, use relaxed versioning:
| Change Type | Bump |
|---|---|
| Large new features | Minor (0.x.0 → 0.(x+1).0) |
| Bug fixes, small features, refactors, docs | Patch (0.x.y → 0.x.(y+1)) |
| Breaking changes | No strict semver; use minor or patch as appropriate |
Override cargo-smart-release's version suggestion by editing Cargo.toml before --execute; it respects manual version edits when the current version isn't yet released.
cargo-smart-release uses the crate name (as published to crates.io), which may differ from the directory/package name. Check Cargo.toml:
[package]
name = "flow-fcs" # This is the crate name for cargo smart-release
cargo changelog --write)--execute only after approvalgit tag -l '<crate>-v*'); create and push any missing tags