release-process

Enforce semver validation, token checks, and automated deployment workflows for releases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates release-related disasters caused by manual errors, incorrect token types, or invalid versioning by enforcing a strict, step-by-step validation and deployment runbook.

Core Features & Use Cases

  • Automated Validation: Ensures semver compliance, verifies NPM_TOKEN types, and checks branch state before any release work begins.
  • Release Orchestration: Guides the user through version bumping, tagging, GitHub release creation, and workflow monitoring.
  • Safety Guardrails: Provides clear rollback procedures and prevents common pitfalls like 4-part versioning or accidental draft releases.

Quick Start

Execute the release-process skill to validate the current repository state and begin the automated release workflow for the next version.

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 releases for a multi-package monorepo?

Automate npm releases for a multi-package monorepo by enforcing step-by-step validation, version bumping, git tagging, and GitHub release publication. This prevents common failure modes like invalid version strings and incorrect npm authentication tokens.

What is the best way to prevent invalid semver and npm token errors during deployment?

Prevent invalid semver and npm token errors during deployment by running automated validation checks before any release work begins. This verifies semver compliance, checks NPM_TOKEN types, and validates branch state to ensure operational reliability.

How does semver validation work for automated GitHub release workflows?

Semver validation for automated GitHub release workflows works by enforcing strict version string compliance before tagging. It prevents 4-part versioning and accidental draft releases through safety guardrails and clear rollback procedures.

Can I use this release process for multi-package monorepos without manual versioning?

Yes, you can use this release process for multi-package monorepos without manual versioning. It guides the entire end-to-end lifecycle, orchestrating version bumping, git tagging, and workflow monitoring automatically.

What should I do if a git tag or GitHub release publication fails?

If a git tag or GitHub release publication fails, follow the provided clear rollback procedures. Safety guardrails prevent common pitfalls like accidental draft releases, ensuring operational reliability throughout the deployment workflow.