Release Manager Automation
A release-manager workflow collection for shipping versions safely: draft release notes from Conventional Commits, govern commits, triage red CI, checkpoint risky changes, and generate changelog artifacts before tagging.
Open the source and read safety notes before installing.
Safety notes
- Release automation proposes notes and bumps—humans must approve tags and publishes.
- CI triage reads workflow logs; treat log content as untrusted input.
- Review each linked entry's safety notes before enabling hooks or skills.
Privacy notes
- Release notes commands include commit messages in model context—scrub sensitive subjects.
- Workflow completion hooks may echo branch names and paths in notifications.
Prerequisites
- Git repository with tags and GitHub Actions visible to authenticated gh CLI.
- Claude Code with hooks enabled for workflow completion reporting.
- Team agreement on Conventional Commits and SemVer bump rules.
Schema details
- Install type
- copy
- Reading time
- 2 min
- Difficulty score
- 50
- Troubleshooting
- Yes
- Breaking changes
- No
- Items
- 6 entries
- Estimated setup
- 40 minutes
- Difficulty
- intermediate
Full copyable content
Install commit and checkpoint helpers first, then CI triage and release-notes commands, and finish with git-cliff changelog skill before tagging a release.About this resource
What this collection sets up
A release-manager path from day-to-day commits through green CI to drafted notes and changelog artifacts. It complements broader maintainer bundles by focusing on the cut-release sequence rather than general PR queue operations.
Workflow
- Use
git-smart-commitfor Conventional Commit messages during the release branch. - Run
checkpoint-managerbefore risky refactors near release freeze. - Clear red CI with
ci-failure-triagebefore tagging. - Draft grouped notes with
release-notes-drafting. - Apply
git-cliff-release-changelog-capability-packwhen teams prefer git-cliff output. - Optionally attach
workflow-completion-reportfor session summaries during release week.
Duplicate Check
Complements github-maintainer-operations (broader maintainer index). This
collection focuses narrowly on release-manager automation steps and changelog tooling.
Source citations
Add this badge to your README
Show that Release Manager Automation is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/collections/release-manager-automation)How it compares
Release Manager Automation side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Release Manager Automation A release-manager workflow collection for shipping versions safely: draft release notes from Conventional Commits, govern commits, triage red CI, checkpoint risky changes, and generate changelog artifacts before tagging. Open dossier | /draft-release-notes - Release Notes Drafting Command for Claude Code Slash command that drafts release notes from the Conventional Commits made since the last release tag. Open dossier | Git-Cliff Release Changelog Capability Pack Skill Expert release-changelog capability pack for git-cliff with conventional commits, deterministic release notes, and low-maintenance versioning. Open dossier | Release Changelog Generation Capability Pack Skill Expert release changelog generation capability pack for drafting, validating, and publishing user-facing release notes from conventional commits, tags, and GitHub Releases with source-backed review matrices and privacy-safe output. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety · Privacy · | Safety ✓ Privacy ✓ |
| Category | collections | commands | skills | skills |
| Source | source-backed | source-backed | first-party | source-backed |
| Author | kiannidev | jony376 | JSONbored | kiannidev |
| Added | 2026-06-16 | 2026-06-04 | 2026-04-11 | 2026-06-15 |
| Platforms | Claude Code | Claude Code | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Release automation proposes notes and bumps—humans must approve tags and publishes. CI triage reads workflow logs; treat log content as untrusted input. Review each linked entry's safety notes before enabling hooks or skills. | ✓Read-only with respect to your repository when refs are validated and passed as git arguments; it only reads git history (tags and commit log) and never creates tags, commits, branches, or release artifacts. Validate the optional ref or discovered tag with `git rev-parse --verify --quiet <ref>^{commit}` and reject refs containing shell metacharacters before reading history. It proposes a version bump and notes for you to review; it does not publish a release or push anything. | — missing | ✓This skill plans release publication; it must not create tags, publish releases, or push version bumps without explicit maintainer approval. Security and breaking-change entries can affect downstream consumers; require owner review before public release. Automated changelog tools may include contributor handles or internal ticket IDs; scrub before publishing. Do not run release scripts or CI publish workflows from unreviewed fork contexts. |
| Privacy notes | ✓Release notes commands include commit messages in model context—scrub sensitive subjects. Workflow completion hooks may echo branch names and paths in notifications. | ✓Commit subjects, bodies, and author names from the selected range are included in the model's context to draft the notes. If commit messages contain internal identifiers, customer names, or unreleased details, those become part of the prompt; review the range before running on a private history. The command writes nothing to disk on its own. | — missing | ✓Changelog drafts may expose unreleased features, customer names, internal URLs, and security fix details. GitHub compare views and release automation logs can include private repository metadata. Redact embargoed vulnerability details and internal-only migration notes from public release text. Keep registry tokens, npm credentials, and signing keys out of prompts and generated notes. |
| Prerequisites |
| — none listed |
|
|
| Install | — | | | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.