release

Plans and executes software releases including versioning, branches, rollouts, and rollback playbooks.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/apuya/react-basics-ui --skill release-apuya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/apuya/react-basics-ui/tree/main/.claude/skills/release
Command: npx skills add https://github.com/apuya/react-basics-ui --skill release-apuya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping software without a defined release process leads to ambiguous version bumps, unmerged hotfixes, unrehearsed rollbacks, and feature flags that outlive their features. This Skill provides a structured release management workflow covering the full lifecycle from scoping to close. ## Core Features & Use Cases - Nine release modes: Plan, Cut, Qualify, Roll, Flag, Hotfix, Rollback, Notes, and Audit, each with a defined output such as a release plan, exit checklist verdict, or rollback procedure. - Versioning and branching discipline: Enforces semver/calver scheme selection, MAJOR/MINOR/PATCH bump rules, release branch merge-back requirements, and hotfixes branched from tags rather than mainline. - npm package adaptation: Tailors the process for registry-published libraries like react-basics-ui, replacing staged rollouts with dist-tags, rollback with deprecate-and-roll-forward, and deriving the bump from a .d.ts API diff. - Use Case: A maintainer preparing the react-basics-ui 2.0.0 release uses the Skill to confirm the breaking API changes require a MAJOR bump, run the pre-publish checklist (lint, tsc, vitest, build, npm pack --dry-run), and draft migration notes for each removed prop. ## Quick Start Ask the assistant to plan the next release of the package, including the version bump justification, pre-publish checklist, and release notes with migration steps.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between a MAJOR, MINOR, or PATCH version bump?

Use semver bump rules: MAJOR when consumers must do work to absorb the change, MINOR for additive backward-compatible changes, and PATCH for fixes without interface changes. For libraries, diff the generated .d.ts files before and after; removed exports or narrowed types mean MAJOR.

How do I roll back a bad npm package release?

You cannot recall a published npm version, so publish a fixed patch immediately as a roll-forward. Then run npm deprecate on the bad version with an upgrade message, and repoint the latest dist-tag to a good version if needed.

Should a hotfix branch from mainline or from a tag?

A hotfix must branch from the tag being patched, not from mainline. Branching from mainline pulls in unrelated changes, and the hotfix must merge back to mainline and any supported release branches to prevent the bug reappearing.

What is the npm equivalent of a staged rollout?

Publish pre-releases with npm publish --tag next so the release stays off the latest tag and npm install does not pick it up. Consumers opt in by tag rather than by percentage-based cohort ramps.

When should a feature flag be retired?

Retire a flag when its cleanup trigger fires, such as being at 100 percent for a defined window. Remove the code branch, delete the flag definition and obsolete tests, and close the flag record; a flag at 100 percent for months is dead code.