release-manager · borghei — Claude Code skill: what it does, how to install
release-manager — a skill for Claude Code, Codex, Cursor, Copilot and Gemini CLI that turns git log output or a JSON plan into a changelog, a SemVer bump and a release readiness score. Run it before every release or hotfix.
LicenseRef-MIT-Commons-Clause 132 installs ★ 1,183 updated 2026-11-08
npx skills add borghei/Claude-Skills --skill release-manager -a claude-codeWhat release-manager does
The skill runs on six platforms: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. Three Python scripts — changelog_generator.py, version_bumper.py and release_planner.py — work on piped text or a local file and do not need a live repo checkout.
changelog_generator.py produces Keep-a-Changelog Markdown or JSON. version_bumper.py reads conventional-commit types to pick MAJOR, MINOR or PATCH; the sample log includes two ! commits, which push 1.2.3 to 2.0.0. release_planner.py takes a JSON plan, computes a readiness score, and outputs a checklist, rollback runbook and stakeholder message templates via --include-rollback --include-communication. The sample plan comes back BLOCKED at 72.2% with three named blockers.
Two inputs cause wrong output. Passing git log --oneline hides BREAKING CHANGE: footers, so only ! commits count and the bump lands at MINOR instead of MAJOR — use full git log format when the team writes footers. The generated rollback runbook uses generic steps and time estimates; replace them with the real commands for the target system before treating the runbook as executable.
What it helps with
- generate a changelog from a commit range
- calculate the next SemVer version from conventional-commit types
- score release readiness and surface blockers from a plan JSON
- build a rollback runbook and stakeholder comms for a hotfix
- audit which commits are non-conventional and would be dropped
Example prompts for the agent
- Run
changelog_generator.pyonassets/sample_git_log.txtand produce a changelog for version 2.0.0 - Pipe
git logfrom v1.4.0 to HEAD intoversion_bumper.pywith current version 1.4.0 and show the analysis - Score
plan.jsonwithrelease_planner.py, include the checklist and rollback runbook, list all blockers
How to install release-manager
1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill release-manager -a claude-code2Manually: put the files in place
~/.claude/skills/release-manager/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-manager/
1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill release-manager -a codex2Manually: put the files in place
.agents/skills/release-manager/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill release-manager -a cursor2Manually: put the files in place
.cursor/skills/release-manager/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install borghei/Claude-Skills engineering/release-manager/SKILL.md2Manually: put the files in place
.github/skills/release-manager/SKILL.md1Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill release-manager -a gemini-cli2Platform CLI
gemini skills install https://github.com/borghei/Claude-Skills --path engineering/release-managerManually: put the files in place
.devin/skills/release-manager/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add borghei/Claude-Skills --skill release-manager -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release-manager
How do I install release-manager in Claude Code?
Run npx skills add borghei/Claude-Skills --skill release-manager -a claude-code. The skill file lands at ~/.claude/skills/release-manager/SKILL.md.
What does the release-manager skill do?
It converts git log output into a changelog and SemVer bump, and turns a JSON release plan into a readiness score with a checklist, rollback runbook and comms templates.
How is release-manager different from release-orchestrator?
release-manager works offline on commit text and a plan file. release-orchestrator connects to a live checkout to run preflight checks, scan for secrets and push tags.
Similar skills
All skills for DevOps and infrastructure →release-manager by other authors comes first.