菜单
Create a new release of ratatui-cheese. Use this skill when the user says "make a release", "bump version", "publish", "release", "cut a release", or similar. Assumes the user has already merged any pending PRs — this skill handles version bumping, verification, tagging, and pushing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Review the ratatui-cheese repository from four distinct perspectives: correctness, Rust best practices, API design, and code repetition/refactoring. Use this skill when the user asks for a repo review, design review, code audit, API critique, refactoring suggestions, or requests written review output for this project. Trigger even when the user only mentions reviewing "this repo", "the codebase", "the library API", or asks for findings to be written into files.
Create a new widget module in the ratatui-cheese project. Use this skill whenever the user wants to add a new widget, component, or UI element to the project. Also trigger when the user mentions creating a spinner, list, input, textarea, button, or any TUI component, or says things like "add a new widget", "create a component", "build a new module". Even if the user just says something like "let's do a spinner next" in the context of this project, use this skill.
基于 SOC 职业分类
| name | release |
| description | Create a new release of ratatui-cheese. Use this skill when the user says "make a release", "bump version", "publish", "release", "cut a release", or similar. Assumes the user has already merged any pending PRs — this skill handles version bumping, verification, tagging, and pushing. |
Create a new versioned release. The GitHub Action (.github/workflows/release.yml) handles publishing to crates.io and creating the GitHub release — this skill just prepares and pushes the tag.
main branch with a clean working treegit checkout main
git pull origin main
git status # must be clean
If not on main or working tree is dirty, stop and tell the user.
Read the current version from crates/ratatui-cheese/Cargo.toml. Look at the commits since the last tag to understand what changed, then suggest a version bump with reasoning:
Present the suggestion using AskUserQuestion with the three options and the suggested one marked as recommended. The user picks the final version. Do NOT proceed without their confirmation.
Current version is in:
crates/ratatui-cheese/Cargo.toml (line 3, version = "x.y.z")Update the version in crates/ratatui-cheese/Cargo.toml. Then run cargo check to regenerate Cargo.lock.
If the major or minor version changed, also update the version in:
README.md (the ratatui-cheese = "X.Y" in the install section)crates/ratatui-cheese/README.md (same)just all
All tests, clippy, formatting, and dead-code checks must pass.
git add crates/ratatui-cheese/Cargo.toml Cargo.lock
# Also add READMEs if major version changed
git commit -m "chore: bump version to X.Y.Z"
git tag vX.Y.Z
git push origin main
git push origin vX.Y.Z
Pushing the tag triggers the release workflow which:
gh run list --limit 1
Tell the user to check the GitHub Actions tab for the release workflow status.