release

Cuts tagged stable or beta releases after verifying CI status and updating the changelog.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/witwave-ai/witwave --skill release-witwave-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/witwave-ai/witwave/tree/main/.agents/self/iris/.claude/skills/release
Command: npx skills add https://github.com/witwave-ai/witwave --skill release-witwave-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cutting a release by hand is error-prone: tagging on a red CI, forgetting the changelog, or shipping a partial release when a publish workflow fails. This Skill automates the safe pre-tag work for a tag-driven release pipeline so every release is verified, versioned, and watched to completion. ## Core Features & Use Cases - CI gating before tagging: Verifies the latest run of every workflow on the default branch is green and refuses to tag on failures, in-progress runs, dirty trees, or unpushed commits. - Version inference and changelog generation: Infers patch or minor bumps from conventional commits since the last tag, generates a Keep-a-Changelog entry grouped by component, formats it with a pinned prettier version, and commits it (stable releases only). - End-to-end release watching: Pushes the annotated tag, then watches all release workflows (container images, CLI binaries plus Homebrew, Helm charts) to completion and reports exactly which artifacts published or are missing. - Use Case: A teammate says "release" after a feature lands; the Skill syncs the repo, confirms CI is green, infers a minor bump from feat(...) commits, updates CHANGELOG.md, tags v0.12.0, and reports the workflow and artifact URLs once publishing succeeds. ## Quick Start Ask the agent to "release" the primary repository and it will verify CI, infer the version, update the changelog, tag, and report the published artifacts.

Frequently Asked Questions about release

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

FAQPage Schema
How do I cut a release with a tag-driven CI pipeline?▼

Invoke the release skill with "release", "release beta", or an explicit version like "release v0.12.0". It syncs the repo, verifies every workflow on the default branch is green, infers the version bump, updates the changelog, pushes an annotated tag, and watches the publish workflows.

How is the next release version inferred from commits?▼

Commits since the previous tag are scanned for conventional-commit prefixes: feat, BREAKING CHANGE, or ! markers infer a minor bump, everything else infers patch. Major bumps are never inferred pre-1.0 and require an explicit "release major" request.

What happens if CI is failing when I try to release?▼

The skill refuses to tag. It checks the latest run of every workflow on the default branch, not just runs on the release commit, and surfaces the failing workflow names, commits, and run URLs so the underlying breakage can be fixed first.

Does the release skill update the changelog for beta releases?▼

No. Beta releases skip the changelog step entirely; the [Unreleased] section keeps accumulating across the beta cycle and is renamed when the stable version graduates. Only stable releases generate and commit a CHANGELOG.md entry.

What happens if a release workflow fails after the tag is pushed?▼

The skill watches all release workflows to completion and reports a [release-workflow-failed] status listing which artifacts published and which are missing. It does not retry, delete the tag, or auto-recover; the calling agent decides the next step.

Can this skill cut hotfix releases on older version lines?▼

No. Hotfixes branching off an old tag with cherry-picks are explicitly out of scope. The skill only releases from the default branch of the primary repository and does not handle cross-repo releases or tag deletion.