release-manager
Turns conventional-commit logs into a changelog and SemVer bump, and scores a release plan for readiness, rollback and comms
Install / Use
npx skills add borghei/Claude-Skills --skill release-managerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Tags
Our assessment of release-manager
release-manager scores 84/100 on our quality scale, 586th of 755 Operations skills we index.
Its SKILL.md is 6.2 KB long, well organised into 8 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so release-manager is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
release-manager compared with similar skills
All 4 of these similar skills score higher than release-manager; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| release-manager (this skill)by borghei | 84 | 817 | 57d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install release-manager?
- Run
npx skills add borghei/Claude-Skills --skill release-manager. The install tabs above show the steps for each supported agent. - Which AI agents does release-manager work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is release-manager safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is release-manager still maintained?
- The repository was last updated about 2 months ago, so release-manager is actively maintained.
Skill content
View source on GitHubname: 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 author: borghei category: engineering domain: devops tier: POWERFUL 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.
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 |
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
