skills.rest
sachinnair90
sachinnair90COMMUNITY
Explore all skills by this author →
GitHub

release-process

Coordinate safe software releases with semver, Git tags, GitHub Releases, and npm publication.

Updated Apr 3, 2026
Search Tags:#workflow automation#rollback#semver#npm publish#version bump#github releases#release process
One-click install
npx skills add https://github.com/sachinnair90/gitgloss --skill release-process-sachinnair90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill release-process-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined release runbook that prevents versioning mistakes, broken publishes, and tag or workflow mishaps during software releases.

Core Features & Use Cases

  • Pre-release validation: Checks semver correctness, token type, branch cleanliness, tag collisions, and required environment settings before any release action.
  • Release orchestration: Guides version bumps, commits, annotated tags, GitHub Release creation, workflow monitoring, and npm publication verification.
  • Recovery and rollback: Covers deprecation, unpublish options, release deletion, and branch reversion when a release needs to be corrected.
  • Use case: A maintainer preparing a package release can follow this Skill to publish safely, confirm npm availability, and then advance the dev branch to the next preview version.

Quick Start

Use this skill to walk through a safe end-to-end release, from validation and tagging to publication verification and preview-version sync.

Frequently Asked Questions about release-process

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

FAQPage Schema
How do I safely publish an npm package from a clean main branch?▼

To safely publish an npm package, validate semver correctness, ensure a clean main-branch state, apply version bumps, create annotated Git tags, monitor workflows, and verify npm publication using an automation NPM token.

What steps are needed to rollback a broken npm release and revert Git tags?▼

Rolling back a broken npm release involves deprecating or unpublishing the package version, deleting the erroneous GitHub Release, and performing a branch reversion to correct tagging and versioning mistakes.

How do I prevent versioning mistakes when bumping semver for GitHub releases?▼

Preventing versioning mistakes requires pre-release validation of semver correctness, checking for tag collisions, verifying a clean main-branch state, and applying annotated Git tags before creating GitHub Releases.

Do I need an automation NPM token to automate GitHub releases and npm publish?▼

Yes, an automation NPM token is required for npm publication. You also need valid semantic versioning, a clean main-branch state, and proper environment settings to orchestrate GitHub Releases and workflow monitoring safely.

Why should I synchronize the dev branch with a preview version after publishing?▼

Synchronizing the dev branch with a preview version after publishing advances the repository to the next development cycle, preventing versioning collisions and keeping development aligned with the latest published release.

Related Skills

Explore More Software Engineering Skills→
WayneWalterBerryWayneWalterBerry

release-process

Automate npm-based Squad releases with semver validation and rollback procedures.

Community
Advanced
DeDuvaDeDuva
1

release-process

Automate pre-release validation and npm publish commands for multi-package repositories.

Community
Advanced
RheinmirRheinmir

release

Orchestrate version bumps, tests, git tags, npm publishing, and GitHub releases.

Community
Advanced
ragnarok22ragnarok22
5

release

Automate version bumping, release notes, tests, Git tagging, and GitHub releases.

Community
Advanced