Release Notes
When the user needs to write release notes, changelogs, or document what changed in a release. Use when the user says 'write release notes,' 'changelog,' 'what changed,' 'document this release,' 'update the README after launch,' or after completing a significant feature or version bump.
Install
npx skills add 0xranx/agentbrief --skill release-notesgit clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/tech-writer/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 & Changelog You are a technical writer creating release documentation. Your goal is to communicate changes clearly to different audiences: users who want to know what's new, developers who need migration guidance, and stakeholders who need the executive summary. ## Process ### 1. Gather Changes Start by analyzing what changed: ```bash # Get commits since last release git log --oneline v$(previous)..HEAD # Get changed files for scope assessment git diff --stat v$(previous)..HEAD ``` Categorize each change: - **Added** — New features - **Changed** — Modifications to existing behavior - **Fixed** — Bug fixes - **Deprecated** — Features marked for removal - **Removed** — Features removed - **Security** — Vulnerability fixes - **Performance** — Speed/efficiency improvements ### 2. Write for Your Audience **User-facing release notes** (blog/email): - Lead with the most exciting change - Use screenshots/GIFs for visual changes - Explain benefits, not implementation details - Keep it scannable: headlines + 1-2 sentence descriptions **Developer changelog** (CHANGELOG.md): - Follow [Keep a Changelog](https://keepachangelog.com/) format - Include breaking changes prominently at the top - Link to relevant PRs/issues - Include migration instructions for breaking changes **Internal release summary** (Slack/team): - One paragraph executive summary - Bullet list of key changes - Any known issues or follow-up items - Who contributed (recognition) ### 3. Format
Details
- Skill name
release-notes- Repository
- 0xranx/agentbrief
- Path
briefs/tech-writer/skills/release-notes/SKILL.md- License
- MIT
- Repo updated
- 28 March 2026
FAQ
What does the Release Notes skill do?
When the user needs to write release notes, changelogs, or document what changed in a release. Use when the user says 'write release notes,' 'changelog,' 'what changed,' 'document this release,' 'update the README after launch,' or after completing a significant feature or version bump.
How do I install the Release Notes skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --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 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.
Related skills
Typescript Advanced Types
430xranx/agentbrief
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
Analytics Setup
430xranx/agentbrief
When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.
API Documentation
430xranx/agentbrief
Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.
Review Process
430xranx/agentbrief
Step-by-step workflow for conducting thorough code reviews
Neutron Log
48frankxai/claude-skills-library
Measure whether a token-saving tool actually saves tokens and keeps answers correct. Use before adopting or recommending RTK, headroom, caveman or any compressor, after changing a hook or instruction file, and when someone quotes a savings percentage. Runs a same-task before and after protocol and records only measured numbers.
Todo Discipline
48frankxai/claude-skills-library
Use when starting any complex task (3+ steps) or before declaring work complete. Enforces todo/task state to match reality — merge updates + read verification. Prevents false completion.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.