skills.rest
PlagueHO
PlagueHOCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-process

Validate semver, tokens, and branch state before publishing GitHub releases and npm packages.

2|1|Updated Mar 25, 2026
Search Tags:#automation#workflow#npm#semver#release-management#ci-cd
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill release-process-plagueho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill release-process-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The definitive release runbook for Squad prevents disasters such as mismanaged semver, invalid tokens, and broken automation by providing a standardized, auditable release process.

Core Features & Use Cases

  • Step-by-step validation of semver, token hygiene, branch state, and proper tagging before release.
  • GitHub Release publishing, CI workflow monitoring, and npm publication verification as part of a cohesive release pipeline.
  • Rollback and remediation guidance including unpublishing, deprecation, and tag cleanup for safe recoveries.

Quick Start

Begin by validating the version, verify the automation token, ensure a clean main branch, and execute the release steps exactly as described.

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 release management and prevent invalid version tags?▼

Automate npm release management by enforcing semver validation, verifying automation tokens, and checking branch state before tagging. This release process prevents invalid versions and broken automation by validating package.json synchronization across all workspaces before publishing.

What is the best way to monitor a CI-CD workflow after publishing a GitHub release?▼

Monitor a CI-CD workflow after publishing a GitHub release by tracking pipeline execution status and verifying npm publication output. This release governance process validates that the CI workflow completes successfully and confirms the package is live on the npm registry.

How do I rollback a failed npm release and clean up git tags?▼

Rollback a failed npm release by following documented remediation procedures including unpublishing or deprecating the package and cleaning up git tags. This rollback path ensures safe recovery across main and dev flows when a workflow stalls or breaks.

Do I need a clean git state and synchronized package.json versions before releasing?▼

Yes, you need a clean git state and synchronized package.json versions across all workspaces before releasing. This release process enforces technical requirements like semver validity and branch hygiene to prevent disastrous releases caused by stalling or invalid automation tokens.

What are the limitations of manual release management without semver validation?▼

Manual release management without semver validation risks disastrous releases caused by incorrect versions, invalid automation tokens, or stalled CI-CD workflows. Without a standardized release runbook, teams lack auditable rollback procedures and branch state verification for safe recoveries.

Related Skills

Explore More Software Engineering Skills→
Chorus-AIDLCChorus-AIDLC
1.1k

release

Automate Chorus releases with CHANGELOG updates, version bumps, PRs, tags, and GitHub release notes.

Official
Intermediate
christianhellechristianhelle
413

release-process

Automates secure release publishing with SemVer checks, GitHub tagging, and npm rollback safeguards.

Community
Advanced
RheinmirRheinmir

release

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

Community
Advanced
WayneWalterBerryWayneWalterBerry

release-process

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

Community
Advanced