Release Management
ruby-git/ruby-git
Prepares and publishes new releases of the ruby-git gem including version bumps, changelog updates, tagging, and gem publishing.
Automates release management with changelog generation, semantic versioning, and release readiness checks.
Install Release Manager
$ npx skills add borghei/Claude-Skills --skill release-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills release-manager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/release-manager .claude/skills/release-manager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-manager into .claude/skills/release-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-manager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/release-managerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill release-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills release-manager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/release-manager .agents/skills/release-manager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-manager into .agents/skills/release-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-manager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill release-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills release-manager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/release-manager .cursor/skills/release-manager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-manager into .cursor/skills/release-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-manager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/release-manager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill release-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills release-manager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/release-manager .gemini/skills/release-manager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-manager into .gemini/skills/release-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-manager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills release-managerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill release-manager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/release-manager .github/skills/release-manager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-manager into .github/skills/release-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-manager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill release-manager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills release-manager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/release-manager .opencode/skills/release-manager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/release-manager into .opencode/skills/release-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-manager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-manager- GitHub stars
- 874
- Token cost
- ~1.6k tokens
- SKILL.md length
- 646 words
- Files
- 16 (incl. references, assets)
- Skills in repo
- 364
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automates release management with changelog generation, semantic versioning, and release readiness checks.
- Preparing releases
- SKILL.md covers Core Capabilities, When to Use, Clarify First and Tools, plus 3 more sections
- Runs Python scripts from its folder; calls python and git
- Generating changelogs
What it does
Release Manager is an agent skill from borghei/Claude-Skills. Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including reference files and assets (for example `README.md`, `assets/sample_commits.json` and `assets/sample_release_plan.json`).
It sits in Development, covering Changelog and release notes, Feature launches and release readiness and Open source maintenance. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Preparing releases
- Generating changelogs
- Bumping versions
- Validating release candidates
Example prompts
- “Use the release-manager skill to automate release management with changelog generation, semantic versioning, and release readiness checks”
- “/release-manager”
Requirements
- Python 3
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
pythongit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Manager loads about 1.6k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 646 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 646 words, ~1,594 tokens.
Download SKILL.mdSave it as
.claude/skills/release-manager/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.- name
- release-manager
- description
- Automates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.
- license
- MIT + Commons Clause
- metadata.version
- 1.1.0
- metadata.author
- borghei
- metadata.category
- engineering
- metadata.domain
- devops
- metadata.tier
- POWERFUL
- metadata.updated
- 2026-06-17
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.
Tools
| Tool | Purpose | Command |
|---|---|---|
changelog_generator.py | Generate Keep-a-Changelog from conventional commits | git log --oneline v1.0.0..HEAD | python changelog_generator.py --version 1.1.0 --format both |
version_bumper.py | Determine SemVer bump + emit bump commands | git log --oneline v1.0.0..HEAD | python version_bumper.py --current-version 1.0.0 --analysis |
release_planner.py | Assess release readiness, checklist, rollback, comms | python release_planner.py --input release-plan.json --include-checklist --include-rollback |
References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- references/workflows-and-tool-reference.md — quick start, the 3 core workflows with checkpoints, version-bump rules, rollback triggers, anti-patterns, troubleshooting table, success criteria, and the full CLI flag reference for all three scripts. Read when running a release or looking up a flag.
- references/conventional-commits-guide.md — conventional-commit format, types, and footer conventions. Read when fixing commit hygiene so changelog/version tooling works.
- references/hotfix-procedures.md — severity classification (P0–P3), hotfix procedures, and best practices across workflows. Read when shipping an emergency fix.
- references/release-workflow-comparison.md — Git Flow vs GitHub Flow vs Trunk-based, with structure, branch types, and trade-offs. Read when choosing or aligning a branching model.
Show full SKILL.md (235 more words)Show less
Scope & Limitations
This skill covers:
- Parsing conventional commits and generating structured changelogs in Markdown and JSON formats
- Determining semantic version bumps (major/minor/patch) with pre-release support (alpha, beta, rc)
- Assessing release readiness across features, quality gates, approvals, and timelines
- Generating rollback runbooks, communication plans, and release checklists from structured input
This skill does NOT cover:
- Actual CI/CD pipeline execution or deployment automation (see
engineering/ci-cd-pipeline-generator) - Live monitoring, alerting, or incident response during deployments (see
engineering/monitoring-alerting-setup) - Code review processes or pull request management (see
engineering/code-review-automation) - Infrastructure provisioning, container orchestration, or environment management (see
engineering/infrastructure-as-code)
Integration Points
| Skill | Integration | Data Flow |
|---|---|---|
engineering/ci-cd-pipeline-generator | Embed changelog generation and version bumping as pipeline stages | Git log output flows into changelog_generator.py; version bump output feeds pipeline tagging steps |
engineering/code-review-automation | Validate that PR commits follow conventional commit format before merge | Commit messages validated upstream ensure clean input for changelog generation |
engineering/monitoring-alerting-setup | Define rollback triggers based on monitoring thresholds from the rollback runbook | Rollback trigger thresholds (error rate >2x, latency >50%) feed into alert rule configuration |
engineering/api-design-reviewer | Breaking API changes flagged by the reviewer map to MAJOR version bumps | API review findings populate breaking_changes arrays in the release plan JSON |
engineering/infrastructure-as-code | Deployment steps in the rollback runbook reference infrastructure rollback commands | Rollback runbook command fields contain infrastructure-specific commands (kubectl, DNS, load balancer) |
project-management/release-planning | Release plan JSON structure aligns with PM release tracking artifacts | PM feature lists and approval statuses feed directly into release_planner.py input format |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 15 other files (references, assets) in engineering/release-manager of borghei/Claude-Skills.
- SKILL.md
- README.md
- assets/sample_commits.json
- assets/sample_git_log.txt
- assets/sample_git_log_full.txt
- assets/sample_release_plan.json
- changelog_generator.py
- expected_outputs/changelog_example.md
- expected_outputs/release_readiness_example.txt
- expected_outputs/version_bump_example.txt
- references/conventional-commits-guide.md
- references/hotfix-procedures.md
- references/release-workflow-comparison.md
- references/workflows-and-tool-reference.md
- release_planner.py
- version_bumper.py
Open the folder on GitHubat commit c9a1487
Compare with similar skills
Release Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Manager this skillborghei/Claude-Skills | 874 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Release Managementruby-git/ruby-git | 1.8k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 69k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Herdr Pre-Release Auditherdrdev/herdr | 43k | — | ~289 | Automated safety check: Pass | Apache-2.0 | |
| Desktop What's New Dialogcline/cline | 70k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Megaphone ReleaseKuberwastaken/megaphone | 169 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Herdr Pre-Release Audit
herdrdev/herdr
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's…
Desktop What's New Dialog
cline/cline
Guides publishing a one-time What's new dialog in the Cline desktop app: deciding if one is due, picking highlights from the changelog and editing one content file.
Megaphone Release
Kuberwastaken/megaphone
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
Create Release Checklist
software-mansion/smelter
Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.
More from borghei/Claude-Skills
All 364 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Release Manager
What does Release Manager do?
Automates release management with changelog generation, semantic versioning, and release readiness checks. Release Manager is an agent skill from borghei/Claude-Skills. Automates release management with changelog generation, semantic versioning, and release readiness checks.
When should I use Release Manager?
Release Manager fits situations like: preparing releases; generating changelogs; bumping versions; validating release candidates.
How do I install Release Manager in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill release-manager -a claude-code`. Or copy the skill folder (engineering/release-manager in borghei/Claude-Skills) into .claude/skills/release-manager in your project. Claude Code loads it when a task matches its description.
How do I install Release Manager in Codex?
Run `npx skills add borghei/Claude-Skills --skill release-manager -a codex`. Or copy the skill folder (engineering/release-manager in borghei/Claude-Skills) into .agents/skills/release-manager in your project. Codex loads it when a task matches its description.
Can I use Release Manager in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill release-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-manager, .gemini/skills/release-manager, .github/skills/release-manager and .opencode/skills/release-manager in your project.
What does Release Manager need to run?
Going by SKILL.md and its folder, Release Manager needs Python for the scripts in its folder and the command-line tools its instructions call (python and git). Our summary lists: Python 3; Docker.
Does Release Manager access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Release Manager safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Manager use?
Release Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Manager use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.
What are the alternatives to Release Manager?
Skills that share tags, products or a category with Release Manager: Release Management (ruby-git/ruby-git, 1.8k stars), Mole Release Notes Publisher (tw93/Mole, 69k stars), Herdr Pre-Release Audit (herdrdev/herdr, 43k stars) and Desktop What's New Dialog (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Manager?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.