release-process

Name: release-process
Availability: InStock
Author: jperezdelreal

Automate version bumps, tagging, and publishing with semver validation and token checks.

Updated Apr 6, 2026

Search Tags:#automation #git #versioning #release #semver #ci-cd #npm-token

Ready to run

npx skills add https://github.com/jperezdelreal/GymBro --skill release-process-jperezdelreal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill release-process-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This release runbook standardizes and automates the deployment workflow to prevent post-release disasters by enforcing checks and guardrails.

Core Features & Use Cases

Semver validation before any release.
Branch/state checks to ensure a clean, up-to-date main branch.
Token verification to ensure only automation tokens are used for publishing.
Guided release steps covering version bumps, tagging, GitHub Releases, and CI/CD triggers.

Quick Start

Follow this runbook to execute a safe, compliant release without improvisation.

Frequently Asked Questions about release-process

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

FAQPage Schema

How do I automate a safe release process across multiple packages?▼

Automate a safe release process by enforcing a strict sequence of checks, including semver validation, branch state verification, and automation-token checks before version bumping and publishing. This standardized runbook prevents post-release disasters across multiple packages and CI/CD steps.

Why do I need npm token verification before publishing a release?▼

Npm token verification is needed before publishing to ensure only valid automation tokens are used for CI/CD triggers and package publishing. This guardrail prevents unauthorized or manual deployments, enforcing a compliant and safe release sequence across your squads.

What's the best way to validate semver before a version bump?▼

The best way to validate semver before a version bump is to apply automated release runbook checks. Validating semantic versioning early ensures version increments are compliant before any tagging, GitHub Releases, or CI/CD pipeline triggers occur.

How do I ensure my main branch is clean and up-to-date before tagging a release?▼

Ensure your main branch is clean and up-to-date by enforcing branch and state checks prior to tagging. The release runbook automates these checks to verify repository state, preventing incomplete or conflicting code from being released.

Can I use this release runbook for coordinating version bumps across my squad?▼

Yes, you can use this release runbook for coordinating version bumps across your squad. It applies specifically to teams coordinating version bumps, tagging, and publishing, enforcing a strict sequence of steps to guide a safe and compliant release.

What steps are required to trigger CI/CD pipelines for a GitHub release?▼

Steps required to trigger CI/CD pipelines include verifying automation tokens, validating semver, bumping versions, and creating tags. Following this guided sequence ensures GitHub Releases and subsequent CI/CD triggers execute safely without improvisation.