Skip to main content
skill CX Codex

release-management — Claude Code skill: what it does, how to install

release-management creates GitHub releases with gh release, picks a semver version and builds notes from merged PRs. Handy when you tag a version or publish a changelog.

MIT 220 installs ★ 305 updated 2026-11-21

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add yonatangross/orchestkit --skill release-management -a claude-code
Open on GitHub

What release-management does

The skill runs a GitHub release from version to published notes through gh release. It picks the next MAJOR.MINOR.PATCH number and builds notes from merged PRs. The release can go out as a draft (--draft) or a prerelease (--prerelease). Notes are generated from PRs by default in the examples, or you pass your own with --notes or --notes-file.

Before it starts, the agent registers tasks with TaskCreate: one parent and three phases for version and changelog, release creation, and verification with an announcement. The phases run in order. Longer procedures live in references/, including release and hotfix workflows, changelog templates and a tag-triggered GitHub Actions workflow. The agent loads them only when needed.

Without the gh CLI the skill has nothing to run, and it lists Claude Code 2.1.277+ as the compatible version. gh release verify checks release attestation and needs gh CLI 2.86.0+. The skill's own rule is to tag main only, never feature branches.

What it helps with

  • build release notes from merged PRs
  • choose the next patch, minor or major version
  • publish a beta as a prerelease
  • create a draft and review notes before publishing
  • attach build archives to a release

Example prompts for the agent

  • Create a draft release v1.2.0 with notes from merged PRs
  • Cut v1.2.0-beta.1 as a prerelease with gh release create
  • Pick the next semver version and attach ./dist/app.zip to the release

How to install release-management

1Skills CLI (Vercel)

npx skills add yonatangross/orchestkit --skill release-management -a claude-code

2Manually: put the files in place

~/.claude/skills/release-management/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release-management/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about release-management

How do I install release-management in Claude Code?

Run npx skills add yonatangross/orchestkit --skill release-management -a claude-code. The skill file ends up at ~/.claude/skills/release-management/SKILL.md.

What does release-management do?

It creates GitHub releases through gh release: it determines the semver version, generates notes from PRs, and handles drafts and prereleases. It also uploads files to a release and verifies its attestation.

What does release-management need to run?

The gh CLI and Claude Code 2.1.277+. The gh release verify command also requires gh CLI 2.86.0+.

Source text

SKILL.md · MIT
---
name: release-management
license: MIT
compatibility: "Claude Code 2.1.277+. Requires gh CLI."
description: "Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs."
context: inherit
user-invocable: false
disable-model-invocation: true
effort: low
model: haiku
metadata:
  archive-candidate: "pending an outside usage signal"
  category: document-asset-creation
  version: "1.0.0"
  author: "OrchestKit"
  complexity: "low"
  tags: "git, github, releases, versioning, changelog, automation"
allowed-tools: "Read Glob Grep Bash Write Edit TaskCreate TaskUpdate TaskList"
---

# Release Management

Automate releases with `gh release`, semantic versioning, and changelog generation.

> **CC ≥ 2.1.118 (M122):** `claude plugin tag <version>` validates the plugin manifest hierarchy (marketplace.json, plugin.json, package.json, version.txt) before tagging. Runs `--dry-run` in CI before release-please opens its release PR; catches manifest drift early. See `src/skills/chain-patterns/references/plugin-tag.md`.

## CRITICAL: Task Management is MANDATORY (CC 2.1.16)

**BEFORE doing ANYTHING else, create tasks to track progress:**

```python
# 1. Create main task IMMEDIATELY
TaskCreate(
  subject="Release: {version}",
  description="Creating release with semantic versioning and changelog",
  activeForm="Releasing {version}"
)

# 2. Create subtasks for each release phase
TaskCreate(subject="Version & changelog", activeForm="Determining version and generating changelog")
TaskCreate(subject="Create release", activeForm="Creating GitHub release")
TaskCreate(subject="Verify & announce", activeForm="Verifying release and announcing")

# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])

# 4. Update status as you progress
TaskUpdate(taskId="2", status="in_progress")  # When starting
TaskUpdate(taskId="2", status="completed")    # When done
```

## Quick Reference

### Create Release

```bash
# Auto-generate notes from PRs
gh release create v1.2.0 --generate-notes

# With custom title
gh release create v1.2.0 --title "Version 1.2.0: Performance Update" --generate-notes

# Draft release (review before publishing)
gh release create v1.2.0 --draft --generate-notes

# Pre-release (beta, rc)
gh release create v1.2.0-beta.1 --prerelease --generate-notes

# With custom notes
gh release create v1.2.0 --notes "## Highlights
- New auth system
- 50% faster search"

# From notes file
gh release create v1.2.0 --notes-file RELEASE_NOTES.md
```

### List & View Releases

```bash
# List all releases
gh release list

# View specific release
gh release view v1.2.0

# View in browser
gh release view v1.2.0 --web

# JSON output
gh release list --json tagName,publishedAt,isPrerelease
```

### Verify Releases (gh CLI 2.86.0+)

```bash
# Verify release attestation (sigstore)
gh release verify v1.2.0

# Verify specific asset
gh release verify-asset v1.2.0 ./dist/app.zip

# Verify with custom trust policy
gh release verify v1.2.0 --owner myorg
```

### Manage Releases

```bash
# Edit release
gh release edit v1.2.0 --title "New Title" --notes "Updated notes"

# Delete release
gh release delete v1.2.0

# Upload assets
gh release upload v1.2.0 ./dist/app.zip ./dist/app.tar.gz
```

---

## Semantic Versioning

```text
MAJOR.MINOR.PATCH
  │     │     │
  │     │     └── Bug fixes (backwards compatible)
  │     └──────── New features (backwards compatible)
  └────────────── Breaking changes

Examples:
  1.0.0 → 1.0.1  (patch: bug fix)
  1.0.1 → 1.1.0  (minor: new feature)
  1.1.0 → 2.0.0  (major: breaking change)

Pre-release:
  2.0.0-alpha.1  (early testing)
  2.0.0-beta.1   (feature complete)
  2.0.0-rc.1     (release candidate)
```

---

## Release Workflows

Standard and hotfix release procedures using git tags and `gh release`.

Load Read("references/release-workflows.md") for step-by-step standard and hotfix release workflows.

---

## Changelog Generation

Auto-generated from PRs, custom `.github/release.yml` templates, and manual CHANGELOG.md format.

Load Read("references/changelog-generation.md") for changelog template examples and Keep-a-Changelog format.

---

## Release Automation & Checklist

GitHub Actions workflow for tag-triggered releases, version bumping script, and pre/post-release checklist.

Load Read("references/release-automation.md") for CI workflow, bump script, and release checklist.

---

## Best Practices

1. **Use semantic versioning** - Communicate change impact
2. **Draft releases first** - Review notes before publishing
3. **Generate notes from PRs** - Accurate, automatic history
4. **Close milestone on release** - Track completion
5. **Tag main only** - Never tag feature branches
6. **Announce breaking changes** - Prominent in release notes

## Related Skills

- `ork:github-operations`: Milestones, issues, and CLI reference
- `ork:github-operations`: Branch management and git operations

## References

Load on demand with `Read("references/<file>")`:

| File | Content |
|------|---------|
| `semver.md` | Semantic versioning rules and decision tree |
| `release-workflows.md` | Standard and hotfix release procedures |
| `changelog-generation.md` | Auto-generated, template, and manual changelog formats |
| `release-automation.md` | GitHub Actions workflow, bump script, and checklist |

© OrchestKit · MIT · yonatangross/orchestkit

Similar skills

All skills for Git and GitHub →

From the same set86

The whole set →
storybook-testing The storybook-testing Claude Code skill guides component testing in Storybook 10. It covers story authoring, visual checks, CI setup, and migration from Storybook 9. CX Codex +1 224installs explore explore spawns 3–5 agents in parallel to map code structure, trace data flows, identify architecture patterns, and assess code health. Useful for quickly understanding an unfamiliar repo or discovering how a large system is designed. CX Codex +1 224installs errors The errors skill sorts Claude Code session failures by type, looks for earlier matches, and suggests recovery steps. It activates after a command, network, or tool error. CX Codex +1 223installs issue-progress-tracking issue-progress-tracking guides GitHub issue ceremonies using the gh CLI by updating progress labels, creating dedicated branches, enforcing atomic commits, and linking PRs. CX Codex +1 221installs llm-integration llm-integration — a collection of 20 production rules for LLM workflows: strict function calling, SSE streaming endpoints, local Ollama deployments, and LoRA tuning. CX Codex +1 218installs fix-issue The fix-issue skill investigates a GitHub issue, applies a tested fix, opens a linked PR, and records ways to prevent the bug from returning. CX Codex +1 217installs review-pr review-pr is a Claude Code skill that reviews a pull request, branch, or diff range with parallel agents. It returns an approve or request-changes verdict before a merge. CX Codex +1 217installs i18n-date-patterns i18n-date-patterns guides an agent through React translations and locale-aware formatting. Use it when adding languages, handling dates or currency, or writing pluralized messages. CX Codex +1 216installs

Project sponsors

Companies that keep this analytics open