Agent skill · software engineering · borghei
release-manager
Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.
Why this skill is useful
Adds 3 executable scripts for changelog generation, semantic version bumping, and release readiness assessment that automate complex release management tasks.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Release Manager The agent automates release management by parsing conventional commits into structured changelogs, determining semantic version bumps, and assessing release readiness with checklists, rollback runbooks, and stakeholder communication plans. Core Capabilities Changelog generation — parse conventional commits since the last tag into Keep-a-Changelog Markdown/JSON, grouped by type with breaking-change highlights and issue links. Semantic version bumping — determine MAJOR/MINOR/PATCH from commit types, support pre-release tracks (alpha → beta → rc), emit bump commands for npm, Python, Rust, Git, Docker. Release readiness — score a release plan across features, quality gates, approvals, and timelines; surface blocking issues. Rollback & comms — generate rollback runbooks with triggers and time estimates, plus stakeholder communication plans with timed message templates. Workflows — changelog+bump, readiness assessment, and expedited hotfix releases, each with validation checkpoints. When to Use Preparing a release — generate the changelog and determine the next version. Validating a release candidate — assess readiness and surface blockers. Shipping a hotfix — expedited fix, pre-release versioning, tested rollback. Auditing commit hygiene — confirm conventional commits drive clean changelogs. Clarify First Before preparing the release, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Last release tag / commit range — defines the changelog window and the basis for the version-bump decision [ ] Release type — standard / hotfix / pre-release (alpha→beta→rc) (selects the workflow and versioning track) [ ] Target ecosystem — npm / Python / Rust / Git / Docker (determines which bump commands are emitted) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/release-manager