What problem does it solve? Cutting a release for a multi-plugin repository involves tedious, error-prone manual work: writing changelog entries, computing semantic version bumps per plugin, creating correctly named git tags, and assembling GitHub release notes with proper attribution. This Skill automates that entire pipeline with mandatory approval gates before any irreversible tag is pushed. ## Core Features & Use Cases - Changelog generation: Updates CHANGELOG.md with a narrative section per release, attributing every change to the plugin whose directory it touched, and crediting PR authors and issue contributors with linked GitHub profiles. - Per-plugin version planning: Computes semantic version bumps (major/minor/patch) for each plugin based on what changed in its directory since the previous release tag, with a confirmation gate when versions need computing. - Safe tagging and publishing: Classifies every tag against the remote (absent, already published, local-only, or colliding), requires explicit approval before creating tags, and publishes a GitHub release with PR and closed-issue attribution. - Use Case: After merging several PRs into the Han repository, run the release skill to generate the v5.1.0 changelog section, bump han-core and han-github versions, tag each changed plugin as {name}--v{version}, and publish the GitHub release notes in one guided flow. ## Quick Start Ask the AI to cut a new Han release from the current repository state, optionally adding the word draft or pause to control publishing behavior.
