Pre-release validation tool for checking commits, versions, and publish dry-runs in Cargo projects.
Install
mkdir -p .claude/skills/release-k1-c && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14710" && unzip -o skill.zip -d .claude/skills/release-k1-c && rm skill.zipInstalls to .claude/skills/release-k1-c
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Check release readiness, preview changelog, and validate publishability. Use when preparing a release or checking version status.Key capabilities
- →Report the current version from `Cargo.toml`
- →List existing Git tags
- →Show unreleased commits since the last tag
- →Validate recent commits against conventional commit format
- →Preview the next changelog entry using `git-cliff`
- →Perform a dry-run of `cargo publish` to verify publishability
How it works
The skill executes a series of Git and Cargo commands to assess the readiness of a Rust project for release, checking versioning, commit history, changelog generation, and package publishability.
Inputs & outputs
When to use release
- →Checking release readiness
- →Validating conventional commits
- →Dry-run testing for package publishing
About this skill
Release Check
Run the following checks to validate release readiness:
Steps
- Current version: Read
Cargo.tomland report the current version - Git tag check: Run
git tag --list 'v*' --sort=-version:refSortto see existing tags - Unreleased commits: Run
git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD --oneline --no-decorateto show commits since last tag - Conventional commit validation: Check that recent commits follow conventional commit format (feat:, fix:, docs:, etc.)
- Changelog preview: If
git-cliffis available, rungit-cliff --unreleasedto preview the next changelog entry. Otherwise, summarize commits manually. - Publish dry-run: Run
cargo publish --dry-run 2>&1to verify the package is publishable
Output
Report a summary:
- Current version:
x.y.z - Commits since last release: N
- Suggested next version based on conventional commits (patch/minor/major)
- Any issues found (missing fields, build errors, etc.)
- Dry-run result (pass/fail)
Notes
- The actual release process is automated via release-plz (GitHub Actions)
- This skill is for local validation before pushing to main
- To publish: push conventional commits to main, release-plz will create a release PR
When not to use it
- →When the project is not a Rust package
- →When the release process is fully automated and no manual checks are needed
- →When the user wants to publish directly without validation
Limitations
- →Assumes a Rust project with `Cargo.toml`
- →Relies on `git-cliff` for changelog preview if available
- →The actual release process is automated via release-plz (GitHub Actions)
How it compares
This skill provides a specific pre-release checklist for Rust projects using conventional commits and Cargo, offering a structured validation process before pushing to main, unlike a general CI/CD pipeline.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 5mo | No flags | Beginner |
| release-skills | 2 | 3mo | Review | Intermediate |
| icn-shipping | 0 | 6mo | No flags | Intermediate |
| ci-pr-helper | 0 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
release-skills
JimLiu
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".
icn-shipping
InterCooperative-Network
Prepare ICN branches for merge with required checks, doc/spec sync, clean git hygiene, and high-quality PR metadata.
ci-pr-helper
lance-format
Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body.
pr
boundless-xyz
Create or update a pull request for the current git changes. Use when the user wants a PR, commit/push for review, or gh pr create flow.
pr
zmerlynn
Push a branch and open a PR with pre-flight checks
release-bump
mikeyobrien
Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish