ship-rolling-candidate

Automate versioning, build orchestration, and GitHub release management for rolling release candidates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires powershell, git, gh-cli, dotnet.

What problem does it solve?

This skill automates the complex, multi-step process of shipping rolling release candidates, eliminating manual errors and ensuring consistent CI/CD verification across Windows, macOS, and Linux.

Core Features & Use Cases

  • Automated Release Lifecycle: Handles version bumping, commit tagging, and GitHub release creation with strict pre-flight validation.
  • Cross-Platform Verification: Enforces mandatory CI checks and visual regression testing to prevent broken builds from reaching users.
  • Use Case: When a new feature is merged, use this skill to autonomously build, test, and publish a release candidate while ensuring all platform-specific hash drifts and build requirements are met.

Quick Start

Trigger the ship rolling candidate skill to initiate the automated release process for the current commit.

Frequently Asked Questions about ship-rolling-candidate

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

FAQPage Schema
How do I automate rolling release candidate deployment for cross-platform .NET applications?

Automate rolling release candidate deployment by orchestrating version bumping, build validation, and GitHub release creation. This ensures consistent cross-platform binary distribution for Windows, macOS, and Linux while enforcing strict CI/CD gatekeeping before publishing.

How does automated release tagging and artifact upload synchronization work across multiple operating systems?

Automated release tagging and artifact upload synchronization works by applying atomic release tags and managing GitHub releases across multiple operating systems. It validates platform-specific hash drifts and build requirements during the release process.

What is the best way to prevent broken builds from reaching users during a GitHub release?

Prevent broken builds from reaching users by enforcing mandatory CI checks and visual regression testing before release creation. This pre-flight validation blocks broken commits from being tagged or published as rolling release candidates.

Do I need PowerShell and the GitHub CLI to automate CI/CD release management?

Yes, you need PowerShell, the GitHub CLI, Git, and the .NET SDK to automate CI/CD release management. These dependencies provide the command-line execution environment required for versioning, building, and GitHub release orchestration.

Can I use this automated release process for a repository other than VPNRouter?

The automated release process is specifically tailored for VPNRouter deployment workflows. It handles the end-to-end pipeline including versioning, cross-platform build orchestration, and GitHub release management for that specific project context.

Why does cross-platform verification matter when publishing rolling release candidates?

Cross-platform verification matters because it prevents platform-specific regressions from reaching users. Enforcing mandatory CI checks across Windows, macOS, and Linux ensures all platform-specific hash drifts and build requirements are met before release publication.