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/hotfix-checklist.md

View on GitHub
# Hotfix Checklist

A hotfix is a release outside the cadence. It runs a shorter gate, not no gate. Use this instead of `release-checklist.md` for any out-of-cadence fix.

If production is actively failing, run `incident-response` first. Mitigate (roll back, turn a flag off) before writing a fix. The hotfix is usually what ships after mitigation.

---

## 1. Qualify

A hotfix is justified only if one of these is true. Record which.

- [ ] Production defect at S1 (severity scale from `ticket-authoring`)
- [ ] Production defect at S2 with no workaround
- [ ] Security fix that cannot wait for the next release
- [ ] Legal or compliance fix with a deadline before the next release

Does not qualify: a feature that missed the cut, an S3 someone is embarrassed about, a request from a single customer with no severity behind it. These wait for the next release. If the next release is too far away for anything, the cadence is the problem.

- [ ] Bug ticket exists with repro steps, severity, and a named fix verification test
- [ ] Release owner (or deputy) approves the hotfix in writing

## 2. Build the fix

- [ ] Branch from the released version tag, not from the main line. The main line holds unreleased work.
- [ ] Change is the smallest that fixes the defect. No refactors, no extra fixes riding along.
- [ ] Fix verification test written or updated, failing before the fix and passing after
- [ ] Second-person review completed

## 3. The shortened gate

| May be shortened | May never be skipped |
|---|---|
| Train schedule: ship now | Second-person review |
| Freeze: none beyond this change | Fix verification test passing on the hotfix build |
| Regression: the targeted set for the touched area, not the full suite | Targeted regression set for the touched area |
| Release notes: one Fixed or Security entry | Version bump (patch under SemVer, next micro under CalVer) |
| Stage dwell times: shortened | Changelog entry |
| Go/no-go meeting: a written decision by the release owner is enough | A known rollback method to the previous version |
| | At least one stage before everyone |

- [ ] Candidate built: `[patch version]-rc.1`
- [ ] Every "never skipped" item above has evidence
- [ ] Release owner records go or no-go with a reason

## 4. Roll out

- [ ] Internal or canary stage first, even if only for minutes
- [ ] Watch signals for the defect's symptom plus overall health
- [ ] Full exposure
- [ ] Defect confirmed gone in production, by the fix verification steps

## 5. Record

- [ ] Changelog entry under the patch version, dated
- [ ] Release tagged
- [ ] Short note to affected users if they saw the defect
- [ ] Support told the fix is live

## 6. Return to the main line

Do this the same day. A hotfix that lives only on a release branch comes back as a regression next release.

- [ ] Fix merged or cherry-picked onto the main line
- [ ] Fix verification test on the main line, passing
- [ ] If the main line has diverged so the fix does not apply cleanly, a separate main-line fix ticket is opened and linked
- [ ] Next release's merged list shows the fix, or shows it already present

## 7. Follow up

Every hotfix produces at least one follow-up item.

- [ ] Follow-up ticket: why the defect escaped the normal gate
- [ ] Follow-up ticket: the test or check that would have caught it
- [ ] For an S1, an after-action review (see `after-action-report`)
- [ ] Hotfix counted in the release history; more than one per cycle for three cycles is a signal about the gate, not about bad luck
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: 472kUpdated 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