release-changelog

Automate version bumps across package.json, Tauri, Cargo, and CHANGELOG.md.

8|5|Updated Jan 20, 2025
One-click install
npx skills add https://github.com/Perseus/pko-tools --skill release-changelog-perseus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Perseus/pko-tools/tree/main/.codex/skills/release-changelog
Command: npx skills add https://github.com/Perseus/pko-tools --skill release-changelog-perseus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation and synchronization of release notes for PKO Tools across package.json, Tauri, Cargo, and CHANGELOG.md, reducing manual toil during releases.

Core Features & Use Cases

  • Automates version bumps across package.json, Tauri, and Cargo and updates the CHANGELOG accordingly.
  • Captures release screenshots via the Tauri MCP workflow and prepares release assets.
  • Supports optional tag/release prep and dry-run workflows for safe release validation.

Quick Start

Run the release-changelog workflow to draft the next release notes and sync all version references.

Frequently Asked Questions about release-changelog

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

FAQPage Schema
How do I automate version bumps across Tauri, Cargo, and package.json for a release?

To automate version bumps, the release-changelog workflow synchronizes version numbers across package.json, Tauri, and Cargo while simultaneously updating your CHANGELOG.md file to ensure all references remain consistent.

What is the best way to generate and sync release notes for a Tauri application?

The best way to generate and sync release notes is using an automated workflow that updates CHANGELOG.md, captures screenshots via the Tauri MCP workflow, and prepares release assets in a single integrated process.

Can I prepare Tauri release metadata and screenshots without pushing commits automatically?

Yes, the workflow enforces local-only changes by default, modifying only local files for release notes and metadata until you explicitly request optional pushes or tags to update the remote repository.

How do I validate a release workflow and changelog updates before publishing?

You can validate a release workflow by running a dry-run process, which safely simulates the version bumps and changelog updates to confirm everything is correct without making permanent changes or pushing commits.

Does Cargo version synchronization work automatically when updating a Tauri app's package.json?

Yes, Cargo version synchronization occurs automatically alongside package.json and Tauri updates, ensuring the Rust backend and frontend version numbers match perfectly without requiring manual intervention.