release-process

Name: release-process
Availability: InStock
Author: barichter

Automate the Squad release workflow with semver and NPM_TOKEN checks.

Updated Apr 12, 2026

Search Tags:#release management #version control #CI/CD #package management #release checklist

Ready to run

npx skills add https://github.com/barichter/squad --skill release-process-barichter

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures a smooth release process for Squad by providing a comprehensive checklist that prevents common release disasters.

Core Features & Use Cases

Pre-Release Validation: Checks for valid semver, NPM_TOKEN verification, branch and tag state, and bump-build.mjs disabling.
Release Workflow: Steps for version bump, commit and tag creation, GitHub release creation, workflow monitoring, npm publication verification, and installation testing.
Manual Publish and Rollback: Procedures for manual publishing and rollback in case of failure or critical issues.

Quick Start

Run the release process to automate the release of a new version of Squad. Follow the detailed checklist provided in the SKILL.md file.

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 package release and version bumping?▼

Automate npm package release by running a step-by-step checklist that validates semver compliance, bumps versions, commits tags, and verifies npm publication. This ensures a smooth deployment workflow from start to finish.

What pre-release validation checks are needed for CI/CD package management?▼

Pre-release validation for CI/CD package management requires checking for valid semver, verifying NPM_TOKEN usage, confirming branch and tag state, and ensuring build scripts are disabled. These checks prevent common release disasters.

How do I monitor GitHub release workflows and verify npm installation?▼

Monitor GitHub release workflows and verify npm installation by following a release workflow checklist that tracks deployment status and tests package installation post-publication. This confirms the released version is accessible and functional.

Can I manually publish a package or rollback a failed release?▼

Yes, you can manually publish a package or rollback a failed release using dedicated procedures for manual publishing and rollback. These steps handle critical issues when the automated release workflow encounters failures.