skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-process

Automate and enforce production release workflows for Squad across versioning, tagging, and publishing.

3|3|Updated Apr 13, 2026
Search Tags:#rollback#github#release#semver#release-management#ci-cd#npm-token
One-click install
npx skills add https://github.com/quaid-app/quaid --skill release-process-quaid-app
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/quaid-app/quaid/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/quaid-app/quaid --skill release-process-quaid-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This runbook provides a definitive, auditable release process for Squad to prevent disasters like v0.8.22 by enforcing strict checks, roles, and sequencing across versioning, tagging, and publishing.

Core Features & Use Cases

  • Step-by-step release validation, coordinated version bumps across workspaces, and formal GitHub Release creation.
  • Enforced checks for semver validity, appropriate NPM token types, clean git state, and tag integrity.
  • Rollback, deprecation, and post-release synchronization procedures to align production and development streams.

Quick Start

Follow the step-by-step runbook to prepare, tag, publish, and verify a production release.

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 production release workflow to prevent disasters?▼

Automating a production release workflow requires enforcing strict checks across branching, versioning, tagging, and publishing. This process validates semver formats and NPM tokens to ensure a clean git state before publishing.

What is the best way to prevent npm publishing failures during a release?▼

Preventing npm publishing failures involves validating NPM_TOKEN types and ensuring proper tag presence before publication. A structured release workflow enforces these checks to handle common failure modes.

How do I enforce semver validation and a clean git state before publishing?▼

Enforcing semver validation and a clean git state requires a step-by-step runbook that checks version formats and git status before tagging. This prevents versioning errors and ensures release integrity.

What is the proper rollback procedure after a failed GitHub release?▼

A proper rollback procedure includes deprecation and post-release synchronization to align production and development streams. This reverses failed publishes while maintaining repository consistency.

Do I need a specific NPM_TOKEN type to publish releases through CI/CD?▼

Yes, a release workflow validates appropriate NPM_TOKEN types to ensure CI/CD publishing succeeds. Using the correct token type prevents unauthorized or failed npm publications during the release process.

How do I coordinate version bumps across workspaces for a GitHub release?▼

Coordinating version bumps across workspaces requires a release playbook that synchronizes versioning, creates formal GitHub Releases, and aligns production and development streams after publishing.

Related Skills

Explore More Product & Management Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
christianhellechristianhelle
413

release-process

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

Community
Advanced
sudhakrmssudhakrms
1

release-process

Automate and govern software releases with validation and rollback procedures.

Community
Advanced
littlebearappslittlebearapps
62

release-coordination

Orchestrate software release workflows from issue auditing to PyPI publishing.

Official
Advanced