han-release

Audit changes, compute plugin version bumps, and generate release notes for the Han ecosystem.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill han-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: han-release
Source: https://github.com/testdouble/han/tree/main/.claude/skills/han-release
Command: npx skills add https://github.com/testdouble/han --skill han-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cut a Han release involves updating CHANGELOG.md with changes since the last release, bumping every changed plugin, tagging the suite version, and publishing a GitHub release whose notes attribute merged PRs and credited issues and contributors. This Skill orchestrates that end-to-end for the parent meta-plugin (han) and its child plugins (han-core, han-github, han-reporting, and future han-* extensions).

Core Features & Use Cases

  • Orchestrates the release plan for the entire Han suite, automatically computing per-plugin bumps according to semantic-versioning rules and generating the release narrative.
  • Updates each plugin's version data in {source}/.claude-plugin/plugin.json and the corresponding marketplace.json entry to reflect the planned targets.
  • Aggregates and formats release notes from the PRs, merged commits, and issue attributions to produce a cohesive changelog and release body.
  • Validates prerequisites (GitHub CLI gh, jq, and a clean Git working tree) and halts safely if any are missing or invalid.
  • Produces a ready-to-publish GitHub release, with options to draft or publish, and writes the final release notes to a temp file for distribution.

Quick Start

Invoke the han-release skill to begin a release workflow, optionally including pause_before_publish or draft flags to control publishing.

Frequently Asked Questions about han-release

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

FAQPage Schema
How do I automate release notes and version bumps for a multi-plugin GitHub repository?▼

Yes, you can draft a GitHub release by running the release workflow with a draft flag, which computes plugin version bumps and writes the final release notes to a temp file for review without publishing to the repository immediately.

What prerequisites do I need to automate semantic versioning and changelog generation from git history?▼

Automating semantic versioning and changelog generation requires a clean git checkout, the GitHub CLI (gh) for repository interactions, and jq for parsing marketplace.json and plugin.json data to validate the environment before proceeding.

How does a release management workflow compute per-plugin version bumps across an ecosystem?▼

A release management workflow computes per-plugin version bumps by analyzing git diff and log data against marketplace.json and plugin.json files, applying semantic-versioning rules to determine the correct target version for each changed extension.

Does automated release management work with newly added plugins and renamed files in a git repository?▼

Automated release management handles newly added plugins and renamed files by auditing complete repository-root changes, ensuring that new plugin.json entries and marketplace.json data are detected and included in the version bump and release notes calculation.

Why would my automated GitHub release workflow halt before computing version bumps?▼

An automated GitHub release workflow halts safely if prerequisite validation fails, specifically when the gh CLI or jq are missing, or when the git working tree is not clean, preventing incorrect release plans from being computed.