skills.rest
CarlosSardo
CarlosSardoCOMMUNITY
Explore all skills by this author →
GitHub

release-process

Enforce semver validation, token integrity, and branch discipline for GitHub Releases and npm publishing.

Updated Aug 23, 2026
Search Tags:#automation#git#npm#release#semver#ci
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill release-process-carlossardo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill release-process-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a definitive, repeatable runbook to govern Squad releases, eliminating ad-hoc mistakes and disastrous misconfigurations. It codifies checks for versioning, token validation, branch discipline, and publish timing to ensure safe, auditable releases.

Core Features & Use Cases

  • Enforces semver-compliant version bumps across multiple packages and repositories
  • Validates NPM automation tokens and prevents CI failures due to 2FA
  • Provides a structured rollback, deprecation, and hotfix workflow
  • Guides end-to-end publishing via GitHub Releases and npm, with guardrails and checks

Quick Start

Trigger the release runbook from the main branch and monitor the publish workflow until all steps complete 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 publishing safely in a CI pipeline?▼

Automate npm publishing safely by enforcing a strict runbook that validates automation tokens, prevents 2FA failures, and checks branch discipline before publishing packages to npm.

Why do my npm releases fail in CI due to 2FA or token issues?▼

npm releases fail in CI when automation tokens lack proper validation or encounter 2FA blocks. A structured release runbook validates tokens beforehand and prevents these publishing failures.

How do I enforce semver compliance for multi-package releases?▼

Enforce semver compliance for multi-package releases by applying a strict versioning runbook that aligns version bumps across multiple repositories and validates semantic versioning rules.

What is the best way to manage a rollback after a failed npm release?▼

Manage a rollback after a failed npm release by following a structured rollback, deprecation, and hotfix workflow that includes post-publish verification and safety measures.

Can I publish GitHub Releases and npm packages simultaneously in one workflow?▼

Yes, you can publish GitHub Releases and npm packages simultaneously by triggering a structured release runbook from the main branch that guides end-to-end publishing with built-in guardrails.

How do I maintain branch discipline during a high-stakes software release?▼

Maintain branch discipline during a software release by triggering the runbook exclusively from the main branch and enforcing strict checks until all publish workflow steps complete successfully.

Related Skills

Explore More Product & Management Skills→
sachinnair90sachinnair90

release-process

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

Community
Advanced
elcoospelcoosp

rm

Manage production release processes with pre-release checklists and rollback procedures.

Community
Advanced
HomericIntelligenceHomericIntelligence
18

install-workflow

Generate GitHub Actions workflows for automated package building and release creation.

Official
Intermediate
Lionad-MorotarLionad-Morotar
7

release-project

Guide software releases from planning to semantic versioning and Git tagging.

Community
Advanced