release-manager
Release Manager
The agent turns a commit range into release notes and the right version number, and a release plan into a readiness verdict with a rollback runbook and stakeholder messages. The tools work on text you give them (piped git log output or JSON), so they run anywhere, including outside the repo.
Pick this or engineering/release-orchestrator: this skill works offline on commit text and a plan file (notes, version, readiness, rollback, comms). release-orchestrator runs against a live checkout: preflight checks, secret scan, tagging and a GO/NO-GO score from repo state.
When to Use
- Preparing a release: generate the changelog and determine the next version.
- Validating a release candidate: score readiness and surface blockers from a plan JSON.
- Shipping a hotfix: pre-release versioning, a rollback runbook and a comms plan.
- Auditing commit hygiene: see which commits are not conventional and get dropped or miscategorised.
Clarify First
Before preparing the release, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- Last release tag / commit range: defines the changelog window and the basis for the bump.
- Release type: standard / hotfix / pre-release (alpha, beta, rc), which selects the workflow and versioning track.
- Target ecosystem: npm / Python / Rust / Git / Docker, which decides the bump commands emitted.