Skip to content

rampstackco/claude-skills / skills/release-management

release-management

Verified

Run the recurring release cycle that turns merged work into a shipped, communicated release: a stated release model, a version derived from the changes, a release candidate and freeze, a written go/no-go gate, staged rollout with an exercised rollback, a hotfix path, and the changelog and release notes. Use this skill whenever the user wants to cut a release, plan or run a release train, decide what version a release should be, freeze code, hold a go/no-go, write a rollout or rollback plan, ship a hotfix, or write release notes, a changelog entry, or a deprecation notice. Triggers on release, cut a release, release notes, changelog, version bump, semver, calver, what version should this be, release train, code freeze, release candidate, RC, go/no-go, rollout plan, staged rollout, canary, rollback plan, hotfix, deprecation notice, release manager, release captain. Also triggers when the user has a set of merged changes and asks how to ship them or what to tell users, even if they never say release.

references/release-notes-template.md

View on GitHub
# Release Notes Template

Three blocks: the changelog entry (the durable record), reader-facing notes (one section per audience), and a deprecation notice. All three come from the same merged list. None is typed from memory.

For launch announcements, blog posts, and in-app campaigns around one headline feature, use `feature-launch-playbook`.

---

## 1. Changelog entry

Keep a Changelog conventions. Newest version at the top. An Unreleased section collects entries as work merges; at the cut, they move under the version.

```
## [Unreleased]

## [3.4.0] - 2026-11-19

### Added
- [What a user can now do, in one line.] ([work item ID])

### Changed
- [What behaves differently, and for whom.] ([ID])

### Deprecated
- [What will be removed, the replacement, and the removal date or version.] ([ID])

### Removed
- [What is gone. Link the earlier deprecation entry.] ([ID])

### Fixed
- [The symptom a user saw, now gone.] ([ID])

### Security
- [What was fixed, at the level of detail your disclosure policy allows.] ([ID])
```

Rules:

- Omit empty categories.
- One line per change, written as the effect on a user, not the code change. "Exports no longer drop rows past 10,000," not "fix off-by-one in paginator."
- Internal items (refactors, test changes, build changes) stay out unless they change behavior.
- Each line keeps its work item ID so the record can be audited against the tracker.

---

## 2. Reader-facing notes

Write one section per audience whose actions differ. Lead with what they need to do. Group by impact, not by team.

```
# [Product] [version] release notes
Released [YYYY-MM-DD]

## Action needed
[Anything a reader must do: update a setting, migrate an integration, re-authenticate.
Each item says who is affected, what to do, and by when. Write "No action needed" if so.]

## For [audience 1, e.g. everyone using the app]
### New
- **[Short name].** [What it does for the reader, in one or two sentences.] [Where to find it.]
### Improved
- **[Short name].** [What is better, in terms the reader notices.]
### Fixed
- [The symptom the reader saw, now gone.]

## For [audience 2, e.g. workspace admins]
[Same shape. Only what admins need beyond the section above.]

## For [audience 3, e.g. API and integration developers]
- Version: [API version] ([what kind of bump and why])
- [New endpoints or fields, with a link to the reference docs]
- [Behavior changes, with before and after]
- [Deprecations, linked to the notice below]

## Known issues
- [Issue, who it affects, workaround, expected fix.]
```

Checks before publishing:

- [ ] Every user-facing merged item has a line in at least one audience section
- [ ] Every line maps to a merged item; nothing is described that did not ship
- [ ] Items still behind a flag that is off are left out or marked "rolling out"
- [ ] Action-needed items name who, what, and when
- [ ] No internal jargon, ticket-only lines, or team names as headings
- [ ] Known issues match the open defects accepted at the go/no-go

---

## 3. Deprecation notice

Publish when the deprecation ships, not when the removal ships. Repeat it in each release until removal.

```
### Deprecation: [feature, endpoint, field, or setting]

What is changing: [The thing being deprecated, in plain words.]
Replacement: [What to use instead, with a link to how.]
Deprecated in: [version, date]
Removal: [version or date. A date, not "a future release."]
After removal: [What happens to a reader who has not moved: error, fallback, silent no-op.]
Who is affected: [How a reader can check: a setting, a log line, an API call pattern, a report.]
Questions: [Where to ask.]
```

Under SemVer, a deprecation ships in a minor release. The removal ships in the next major.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall