Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Generate changelog entries and GitHub releases from git history.
Install Release Notes
$ npx skills add thatrebeccarae/claude-marketing --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thatrebeccarae/claude-marketing release-notes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release-notes .claude/skills/release-notes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-notes" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notes into .claude/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thatrebeccarae/claude-marketing --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thatrebeccarae/claude-marketing release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release-notes .agents/skills/release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-notes" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notes into .agents/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thatrebeccarae/claude-marketing --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thatrebeccarae/claude-marketing release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release-notes .cursor/skills/release-notes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-notes" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notes into .cursor/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thatrebeccarae/claude-marketing.git --path skills/release-notes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thatrebeccarae/claude-marketing --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thatrebeccarae/claude-marketing release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release-notes .gemini/skills/release-notes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notes into .gemini/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thatrebeccarae/claude-marketing release-notesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thatrebeccarae/claude-marketing --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release-notes .github/skills/release-notes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notes into .github/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thatrebeccarae/claude-marketing --skill release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thatrebeccarae/claude-marketing release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thatrebeccarae/claude-marketing.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release-notes .opencode/skills/release-notes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-notes" agent skill from https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/release-notes into .opencode/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-notes- GitHub stars
- 162
- Token cost
- ~1.5k tokens
- SKILL.md length
- 597 words
- Files
- 4
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate changelog entries and GitHub releases from git history.
- Works in 9 steps: Find the last tag or release → Collect commits since last tag → Check merged PRs → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Install, When to Use, Usage and Procedure, plus 1 more section
- Calls gh, git and claude; reaches keepachangelog.com and github.com
What it does
Release Notes is an agent skill from thatrebeccarae/claude-marketing. Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `EXAMPLES.md` and `REFERENCE.md`).
It sits in Development, covering Changelog and release notes, Commit messages and Git workflow. It works with GitHub. The repository describes itself as: A full marketing department for Claude Code. Skill packs for Klaviyo, Shopify, GA4, Looker Studio, paid media, and more. Audit, optimize, and report using natural language. The licence is MIT.
When your agent uses it
- Tasks that involve Changelog and release notes
- Tasks that involve Commit messages
- Tasks that involve Git workflow
Example prompts
- “/release-notes”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a8a63ec. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgitclaude
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
keepachangelog.comgithub.comsemver.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Notes loads about 1.5k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 597 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thatrebeccarae/claude-marketing at commit a8a63ec, republished under its MIT licence (© thatrebeccarae). 597 words, ~1,488 tokens.
Download SKILL.mdSave it as
.claude/skills/release-notes/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- release-notes
- description
- Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
- license
- MIT
- origin
- custom
- author
- Rebecca Rae Barton
- author_url
- https://github.com/thatrebeccarae
- metadata.version
- 1.0.0
- metadata.category
- devops
- metadata.domain
- git
- metadata.updated
- 2026-03-19
- metadata.tested
- 2026-03-19
- metadata.tested_with
- Claude Code v2.1
release-notes
Generate changelog entries and GitHub releases from git history.
Install
claude skill add --from https://github.com/thatrebeccarae/claude-skills/release-notesWhen to Use
- Cutting a release: You have commits ready to ship and need a changelog entry and/or GitHub release.
- Monthly changelog update: You maintain a regular changelog cadence and need to capture everything since the last entry.
- Retroactive changelog: An existing project has no CHANGELOG.md and you want to generate one from the full git history.
Usage
Generate a changelog entry
/release-notes changelog [repo-path]Reads commits since the last tag, categorizes them, and prepends a new entry to CHANGELOG.md.
Create a changelog entry and GitHub release
/release-notes release [repo-path] [version]Does everything changelog does, then creates a GitHub release via gh release create. If version is omitted, a version is suggested based on the changes detected.
Retroactively generate a full changelog
/release-notes init [repo-path]Walks the entire tag history (or full commit history if untagged) and generates a complete CHANGELOG.md from scratch.
Procedure
Step 1 — Find the last tag or release
Run git describe --tags --abbrev=0 to find the most recent tag. If no tags exist, use the initial commit as the starting point. Cross-reference with gh release list --limit 1 to check for GitHub releases that may differ from local tags.
Step 2 — Collect commits since last tag
git log <last-tag>..HEAD --pretty=format:"%H %s" --no-mergesParse each commit message for conventional commit prefixes (type(scope): description). Record the raw message for commits that do not follow conventional format.
Step 3 — Check merged PRs
gh pr list --state merged --search "merged:>YYYY-MM-DD" --json number,title,labels,mergedAt --limit 200Use the date of the last tag as the cutoff. Cross-reference PR titles with commit messages to avoid duplicates. PR titles often provide cleaner descriptions than commit messages — prefer the PR title when a commit is associated with a merged PR.
Step 4 — Categorize changes
Map each commit or PR to a changelog category:
| Prefix / Signal | Category |
|---|---|
feat, feature | Added |
fix | Fixed |
BREAKING CHANGE in body or ! suffix (e.g., feat!:) | Breaking Changes |
docs | Documentation |
refactor, perf | Changed |
chore, ci, build | Maintenance |
deprecate | Deprecated |
remove | Removed |
security | Security |
When conventional commits are not used: Analyze commit message content to infer categories. Look for keywords like "add", "fix", "remove", "update", "refactor", "document". Group ambiguous commits under Changed and flag them for human review.
Show full SKILL.md (248 more words)Show less
Step 5 — Suggest version bump
Apply semantic versioning rules:
- Major bump if any Breaking Changes are present.
- Minor bump if any Added entries exist and no breaking changes.
- Patch bump if only Fixed, Changed, or Maintenance entries.
Present the suggestion with reasoning. The human decides the final version.
Step 6 — Format the changelog entry
Use Keep a Changelog format:
## [X.Y.Z] — YYYY-MM-DD
### Breaking Changes
- Description of breaking change (#PR)
### Added
- Description of new feature (#PR)
### Fixed
- Description of bug fix (#PR)
### Changed
- Description of refactor or improvement (#PR)
### Documentation
- Description of docs change (#PR)
### Maintenance
- Description of chore (#PR)Omit empty categories. Order categories as shown above — Breaking Changes always first.
Step 7 — Human review
Present the formatted entry and suggested version to the user. Wait for explicit approval before writing anything. Highlight any commits that were ambiguously categorized.
Step 8 — Write to CHANGELOG.md
Prepend the new entry after the file header. Never overwrite or reorder existing entries. If CHANGELOG.md does not exist, create it with a standard header:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).Step 9 — Optionally create GitHub release
Only when the user invoked /release-notes release or explicitly requests it:
gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_BODY"Use the changelog entry as the release body. Never create a release without user confirmation.
Key Principles
- Never auto-publish. Every release and changelog write requires explicit human approval.
- Preserve existing entries. Never modify, reorder, or delete previous changelog entries.
- Human-readable over machine-parseable. Write descriptions that make sense to a person reading the changelog, not a parser. Prefer plain language over commit hashes.
- Attribute PRs and authors. Include PR numbers as links. For multi-contributor projects, consider noting first-time contributors.
- When in doubt, ask. If a commit is ambiguous, surface it to the user rather than guessing the category.
© thatrebeccarae, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in skills/release-notes of thatrebeccarae/claude-marketing.
- SKILL.md
- EXAMPLES.md
- LICENSE
- REFERENCE.md
Open the folder on GitHubat commit a8a63ec
Compare with similar skills
Release Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Notes this skillthatrebeccarae/claude-marketing | 162 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Go-Redis Release Preparationredis/go-redis | 22k | — | ~1.1k | Automated safety check: Pass | BSD-2-Clause |
Similar skills
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
- Official
Go-Redis Release Preparation
redis/go-redis
Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
More from thatrebeccarae/claude-marketing
All 55 skills in this repoGoogle Analytics
thatrebeccarae/claude-marketing
Analyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements.
Content Creator
thatrebeccarae/claude-marketing
Comprehensive content marketing toolkit with brand voice analysis, SEO optimization scripts, content frameworks, social media strategy, and content calendar planning.
Klaviyo Analyst
thatrebeccarae/claude-marketing
Klaviyo marketing operations and analyst expertise. An agent skill from thatrebeccarae/claude-marketing.
Klaviyo Developer
thatrebeccarae/claude-marketing
Klaviyo API and developer integration expertise. An agent skill from thatrebeccarae/claude-marketing.
Looker Studio
thatrebeccarae/claude-marketing
Looker Studio (formerly Google Data Studio) expertise. An agent skill from thatrebeccarae/claude-marketing.
Shopify
thatrebeccarae/claude-marketing
Shopify e-commerce platform marketing expertise. An agent skill from thatrebeccarae/claude-marketing.
Related
Works with
Categories
Questions about Release Notes
What does Release Notes do?
Generate changelog entries and GitHub releases from git history. Release Notes is an agent skill from thatrebeccarae/claude-marketing. Generate changelog entries and GitHub releases from git history.
When should I use Release Notes?
Release Notes fits situations like: tasks that involve Changelog and release notes; tasks that involve Commit messages; tasks that involve Git workflow.
How do I install Release Notes in Claude Code?
Run `npx skills add thatrebeccarae/claude-marketing --skill release-notes -a claude-code`. Or copy the skill folder (skills/release-notes in thatrebeccarae/claude-marketing) into .claude/skills/release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Release Notes in Codex?
Run `npx skills add thatrebeccarae/claude-marketing --skill release-notes -a codex`. Or copy the skill folder (skills/release-notes in thatrebeccarae/claude-marketing) into .agents/skills/release-notes in your project. Codex loads it when a task matches its description.
Can I use Release Notes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thatrebeccarae/claude-marketing --skill release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.
What does Release Notes need to run?
Going by SKILL.md and its folder, Release Notes needs the command-line tools its instructions call (gh, git and claude).
Does Release Notes access the network?
SKILL.md names 3 domains. In commands or code: keepachangelog.com, github.com and semver.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Release Notes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Notes use?
Release Notes is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Notes use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Notes?
Skills that share tags, products or a category with Release Notes: Release Bump (jamiepine/voicebox, 57k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
thatrebeccarae (a GitHub user) maintains it in thatrebeccarae/claude-marketing, which has 162 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on May 14, 2026.
Source: thatrebeccarae/claude-marketing on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.