skills.rest
dathere
dathereOFFICIAL
Explore all skills by this author →
Website𝕏@dathereincGitHub

release-prep

Bump version numbers across qsv files and update the changelog for release preparation.

3.7k|104|Updated Dec 11, 2020
Search Tags:#automation#changelog#release#quality#rust#cargo#version-bump
One-click install
npx skills add https://github.com/dathere/qsv --skill release-prep-dathere
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-prep
Source: https://github.com/dathere/qsv/tree/main/.claude/skills/release-prep
Command: npx skills add https://github.com/dathere/qsv --skill release-prep-dathere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the preparation of a qsv release by systematically bumping version numbers across all required files and generating a changelog entry, reducing manual errors and ensuring consistency.

Core Features & Use Cases

  • Bump version strings in Cargo.toml, CLAUDE.md, MCP server manifest, and skill package.json
  • Generate a structured changelog entry from the last release, capturing added features and fixes
  • Validate cross-file consistency and optionally update the MSRV when needed
  • Post-release steps: run validation commands, update artifacts, and document the release

Quick Start

Provide the new version number to the release-prep skill to automatically bump all version strings and create the initial changelog entry.

Frequently Asked Questions about release-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumps across Cargo.toml and other config files for a Rust release?▼

Automate version bumps by applying a target version number across Cargo.toml, CLAUDE.md, MCP server manifests, and package.json simultaneously, ensuring cross-file consistency and preventing mismatches during the Rust release process.

How do I generate a changelog entry from git history before a release?▼

Generate a structured changelog entry from git history by capturing added features and fixes since the last release, ensuring the changelog format is strictly followed and validated for the new version.

What files need version updates when preparing a Cargo release?▼

When preparing a Cargo release, version updates are required in Cargo.toml, CLAUDE.md, MCP server manifest, and package.json to maintain consistent versioning across platforms and release workflows.

How do I validate version consistency across multiple project files?▼

Validate version consistency by checking that version strings match across Cargo.toml, CLAUDE.md, MCP server manifest, and package.json, preventing mismatches and ensuring the changelog format is followed before completing the release preparation.

What's the best way to prevent version mismatches during a release workflow?▼

Prevent version mismatches by automating the release preparation process to systematically bump version numbers across all required files and validate cross-file consistency, reducing manual errors and ensuring uniform versioning.

Related Skills

Explore More Software Engineering Skills→
dhruvinrsonidhruvinrsoni

release-notes

Parse git history to generate changelogs and release notes.

Community
Advanced
YanCheng-goYanCheng-go
3

release

Generate a changelog, bump the version, and open a release PR.

Community
Intermediate
bobmatnycbobmatnyc
15

cargo-publish

Automates validated publishing of Rust crates to crates.io with dependency ordering and git checks.

Community
Advanced
vanman2024vanman2024
3

Version Management

Apply semantic versioning, generate changelogs from commits, and create release tags.

Community
Basic