release-process

Automates end-to-end release workflows with semantic versioning validation, npm/GitHub publishing, and rollback support.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/robpitcher/eShopOnWeb --skill release-process-robpitcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill release-process-robpitcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive, repeatable release runbook to prevent release disasters and human-error during software deployment.

Core Features & Use Cases

  • Step-by-step release validation and execution from main to tagged version.
  • Enforces semver compliance, automation token validation, branch hygiene, and safe publishing to npm and GitHub Releases.
  • Supports rollback and post-release synchronization to next preview.

Quick Start

Follow the step-by-step runbook in this document to perform a release successfully.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I automate npm and GitHub release publishing to prevent version drift?

Automate npm publishing and GitHub releases by validating semantic versioning, branch hygiene, and NPM_TOKEN tokens to enforce synchronization across version bumps, tags, and release notes. This prevents version drift and publishing errors.

What's the best way to ensure safe and auditable software releases?

Ensure safe and auditable software releases by following a repeatable runbook that validates semver compliance, enforces branch hygiene, and synchronizes npm publication with GitHub Releases to prevent human error during deployment.

How do I validate semantic versioning before publishing an npm package?

Validate semantic versioning before publishing an npm package by enforcing semver compliance checks within an automated release workflow, ensuring version bumps, tags, and release notes remain synchronized to prevent publishing errors.

Can I roll back a failed npm and GitHub Release after publication?

Yes, you can roll back a failed npm and GitHub Release after publication. This release management workflow supports rollback and post-release synchronization to transition safely to the next preview version.

Do I need a clean main branch to execute a safe GitHub Release?

Yes, you need a clean main branch to execute a safe GitHub Release. This release runbook enforces branch hygiene validation before proceeding with end-to-end release execution from main to tagged version.