release-guardian

Synchronize version numbers across VoiceLite project files and release workflow.

12|3|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/mikha08-rgb/VoiceLite --skill release-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-guardian
Source: https://github.com/mikha08-rgb/VoiceLite/tree/main/.claude/skills/release-guardian
Command: npx skills add https://github.com/mikha08-rgb/VoiceLite --skill release-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the VoiceLite release process by automating version synchronization across all project files and guiding through a robust deployment workflow, preventing inconsistencies and deployment errors.

Core Features & Use Cases

  • Version Synchronization: Identifies and updates version numbers across .csproj, .iss, package.json, and web download endpoints.
  • Guided Release Workflow: Provides a step-by-step process for pre-release checks, building, packaging, Git tagging, and deployment.
  • Post-Release Verification: Includes steps to verify GitHub Releases and website downloads.
  • Use Case: When preparing for VoiceLite v1.0.97, use this skill to ensure that the version number is correctly updated in the C# project, installer script, web download API, and documentation, then guides through the tagging and deployment to GitHub Actions.

Quick Start

Initiate the release workflow for VoiceLite version 1.0.97, ensuring all version numbers are synchronized and the installer is built correctly.

Frequently Asked Questions about release-guardian

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

FAQPage Schema
How do I synchronize version numbers across multiple project files during a release?

Version synchronization updates version numbers consistently across .csproj, .iss installer scripts, package.json, web APIs, and documentation files. This Skill identifies all version fields in your project and applies updates in a single coordinated action, preventing the deployment errors and user confusion that result from mismatched versions across artifacts.

Can I automate version updates with GitHub Actions and git tagging?

Yes. This Skill integrates with GitHub Actions workflows to automate version propagation, git tagging, and deployment triggers. It guides you through pre-release checks, building, packaging, tagging commits, and deploying to GitHub Releases, eliminating manual steps and reducing human error in the release pipeline.

What files need version updates when releasing a new build?

Release-critical files include C# project files (.csproj), installer scripts (.iss), web package manifests (package.json), download API endpoints, and documentation. This Skill maps all version touchpoints in your codebase and specifies exact updates required for each file type to maintain consistency.

How do I verify that a release deployed correctly after tagging and building?

Post-release verification checks GitHub Releases page and website download endpoints to confirm the new version is live and accessible. This Skill includes verification steps in its guided workflow so you can validate the entire release chain before considering the deployment complete.

What's the best way to manage desktop app, installer, web, and documentation versions together?

Coordinating versions across multiple artifact types requires a unified process that treats all files as a single release unit. This Skill provides a step-by-step release workflow that handles C# desktop builds, Windows installers, web packages, and docs in sequence, ensuring no component falls out of sync.

Do I need to manually edit configuration files for each release?

No. This Skill automates identification and updates of version fields across all configuration and manifest files. Rather than manually locating and editing each file, you describe the target version once and the Skill propagates it consistently, reducing release overhead and error risk.