cut-stable

Promote rolling release candidates to stable versions with verified builds and update paths.

3|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/PavelLizunov/VPNRouter --skill cut-stable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cut-stable
Source: https://github.com/PavelLizunov/VPNRouter/tree/main/.agents/skills/cut-stable
Command: npx skills add https://github.com/PavelLizunov/VPNRouter --skill cut-stable

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, dotnet, powershell.

What problem does it solve?

This skill automates the complex, multi-step process of promoting a rolling release candidate to a stable version, ensuring that all verification gates, build integrity checks, and update paths are validated before production deployment.

Core Features & Use Cases

  • Automated Verification Gate: Validates build status, regression tests, and asset counts across all platforms.
  • Live Update Path Testing: Ensures the new version can successfully auto-update from the previous stable release in a clean environment.
  • Release Orchestration: Handles version bumping, tagging, asset uploading, and cleanup of rolling candidates.

Quick Start

Initiate the stable release promotion process for the current candidate by issuing the cut command after confirming all pre-flight checks are passed.

Frequently Asked Questions about cut-stable

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

FAQPage Schema
How do I automate stable release promotion from a rolling release candidate?

Automate CI/CD release verification by validating build status, regression tests, and asset counts across all platforms to ensure binary integrity before stable promotion. This gate confirms multi-platform asset distribution readiness.

How do I test a zero-downtime update path from the previous stable release?

Test zero-downtime update paths by validating that the new version successfully auto-updates from the previous stable release in a clean environment. This confirms the live update path works before release orchestration and tagging.

Does this release orchestration process work with .NET and PowerShell?

Release orchestration works with .NET and PowerShell because the process depends on the dotnet CLI, PowerShell, and gh command line tools to execute version bumping, tagging, and asset uploading across multi-platform distributions.

What is the best way to manage versioning and cleanup of rolling release candidates?

Manage versioning and cleanup of rolling release candidates through automated release orchestration that handles version bumping, repository tagging, asset uploading, and rolling candidate cleanup after strict quality assurance verification passes.

When do I need automated CI/CD pipelines for binary integrity verification?

You need automated CI/CD pipelines for binary integrity verification when your software release cycle requires strict quality assurance, multi-platform asset distribution, and zero-downtime update path validation before promoting rolling candidates to stable.