release-process

Organize and enforce auditable Squad release workflows across GitHub and npm.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/chdaly/eshop --skill release-process-chdaly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-process
Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/release-process
Command: npx skills add https://github.com/chdaly/eshop --skill release-process-chdaly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes a safe, auditable release process to prevent Squad release disasters.

Core Features & Use Cases

  • Version validation, tag generation, and GitHub release orchestration
  • NPM publish checks, approvals, and rollback procedures
  • Comprehensive pre-release validations and post-release monitoring

Quick Start

Follow this runbook to prepare, execute, and verify a release end-to-end.

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 publication and GitHub releases safely?

Automate npm publication and GitHub releases by enforcing semver validation, checking for a clean working tree, managing tags across main and dev branches, and verifying automation token hygiene before publishing.

What is the best way to handle rollback workflows across main and dev branches?

Handle rollback workflows across main and dev branches by following an enforced runbook that validates tag consistency, reverts version bumps, and coordinates npm unpublish or rollback procedures with post-release validation.

How does semver validation work during a release process?

Semver validation during the release process works by checking the proposed version bump against current tags and branch state, preventing invalid or skipped version increments from proceeding to GitHub release or npm publication.

Do I need a clean working tree before starting a version bump?

Yes, you need a clean working tree before starting a version bump because the release process enforces pre-release validations that block progression if uncommitted changes or automation token hygiene issues are detected.

Can I use this release management runbook for post-release validation?

Yes, you can use this release management runbook for post-release validation, as it includes steps to verify GitHub release orchestration, npm publication status, and tag consistency after the deployment completes.

Why does tag consistency matter when managing GitHub releases?

Tag consistency matters when managing GitHub releases because mismatched tags between local commits and remote branches can cause npm publication failures, break rollback workflows, and compromise the auditable release history.