Release Notes
Write release notes or a changelog entry that tell existing users what they will notice after updating, with the technical detail after it. Use when publishing a release, writing a changelog, or editing release notes.
Install
npx skills add petekp/claude-code-setup --skill release-notesgit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/release-notes ~/.claude/skills/release-notesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Release notes Write for someone who already uses the product. They want to know what will feel different after they update, and whether they have to do anything. Most read the first line and stop. Some scan the highlights. Few read further. Notes they can scan in seconds beat complete notes they skip. ## Gather - List the changes since the last release, such as with `git log --oneline <last tag>..HEAD`. Read the PRs and issues they reference. - Read a change's diff when its commit subject doesn't make the user's experience clear. Describe only effects you can trace to a change. - Find the project's update steps and the apps or platforms it ships to. Look in its release doc, its README, and the last release's notes. ## Shape In this order: 1. **One bold line on the effect users will notice most.** Name the effect, not the area: "Other mods' notes come back above your prompt", not "Fixes for the band". 2. **A picture of the headline change** when it is visible. Reuse the before-and-after image from the PR that made the change when there is one. 3. **Highlights.** Three to five bullets: the changes most users will run into. Each starts with a bold label of a few words, then one short sentence. 4. **Also.** Every other change a user can notice, one bullet each, grouped under a bold heading per app or platform, with "Every app" first. Leave out a group with no changes.
Details
- Skill name
release-notes- Repository
- petekp/claude-code-setup
- Path
skills/release-notes/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the Release Notes skill do?
Write release notes or a changelog entry that tell existing users what they will notice after updating, with the technical detail after it. Use when publishing a release, writing a changelog, or editing release notes.
How do I install the Release Notes skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill release-notes. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Release Notes popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Catch Up
49petekp/claude-code-setup
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
Vignette Todo Run
49petekp/claude-code-setup
Run a batch of Vignette TODO items as a multi-agent worktree run. Use when Pete asks to "run the TODOs", "run items N to M", "do a todo run", or hands over queued items from docs/TODOS.md in the Vignette repo. The orchestrator plans, briefs, and reviews; delegated coding agents do every code change and every verification, each in its own worktree with its own scratch settings; an integrator merges, a reviewer attacks the merge, and the branch is handed to Pete unmerged. Not for a single small fix in the checkout, and not for a repo other than Vignette.
Meeting Prep
43analystacademy/claude-skills
Prepare a comprehensive pre-meeting briefing by pulling together everything you need to walk in ready. Use this skill whenever the user asks to "prep me for my meeting", "what do I have coming up", "brief me before my call", "meeting prep", "get me ready for [meeting name]", or any similar phrasing. Also trigger automatically when the user opens Claude and there is a meeting starting within the next 20–30 minutes — proactively offer the briefing without waiting to be asked. Covers upcoming calendar events, attendee email history, open action items, agenda/notes from the invite, and optional we
Dependency Analyzer
49lis186/SourceAtlas
Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.