New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Notes

by borghei in borghei/Claude-Skills

Structured release notes that translate technical changes (tickets, changelogs, git logs, PRDs) into user-benefit communication.

MITAuto-check passedDevelopment

Install Release Notes

skills CLI
$ npx skills add borghei/Claude-Skills --skill release-notes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills release-notes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/release-notes .claude/skills/release-notes && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release-notes
GitHub stars
874
Token cost
~1.5k tokens
SKILL.md length
618 words
Files
7 (incl. scripts, references, assets)
Skills in repo
364
Repo updated
First seen
Licence
MIT

At a glance

Structured release notes that translate technical changes (tickets, changelogs, git logs, PRDs) into user-benefit communication.

  • Product releases
  • SKILL.md covers Overview, Core Capabilities, Clarify First and Quick Start, plus 3 more sections
  • Runs Python scripts from its folder; calls python
  • Changelog maintenance

What it does

Release Notes is an agent skill from borghei/Claude-Skills. Structured release notes that translate technical changes (tickets, changelogs, git logs, PRDs) into user-benefit communication. Use for product releases, sprint demos, changelog maintenance, or customer release announcements.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/release_notes_template.md`, `examples/wayfinder-v2-1-release-notes.md` and `references/methodology-and-tooling.md`).

It sits in Development, covering Changelog and release notes. It works with Git. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Product releases
  • Changelog maintenance
  • Customer release announcements

Example prompts

  • “/release-notes”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit c9a1487. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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, and up to ~7.6k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 618 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.6k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 618 words, ~1,505 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
release-notes
description
Structured release notes that translate technical changes (tickets, changelogs, git logs, PRDs) into user-benefit communication. Use for product releases, sprint demos, changelog maintenance, or customer release announcements.
license
MIT + Commons Clause
metadata.version
1.0.1
metadata.author
borghei
metadata.category
project-management
metadata.domain
pm-execution
metadata.updated
2026-06-15
metadata.python-tools
scripts/release_notes_generator.py
metadata.tech-stack
release-management, changelog, semantic-versioning

Release Notes Expert

Overview

Transform raw technical changes -- tickets, changelogs, git logs, PRDs -- into clear, user-benefit-oriented release notes. This skill ensures every release communicates value to the right audience in the right tone, via a 5-step methodology: gather input, classify each change into one of five categories, rewrite for user benefit, adjust tone for the audience, and assemble.

When to Use
  • Product Releases -- Announcing new versions to customers, partners, or internal stakeholders.
  • Sprint Demos -- Summarizing what shipped for sprint review audiences.
  • Changelog Maintenance -- Keeping a running log of changes across releases.
  • Customer Communication -- Preparing release announcements for email, in-app, or documentation.

Core Capabilities

  • 5-category classification — New Features, Improvements, Bug Fixes, Breaking Changes, Deprecations with explicit assignment rules
  • User-benefit rewriting — lead with the outcome, plain language, 1-3 sentences; detects developer-perspective phrasing
  • Audience tone guidance — B2B/enterprise, consumer, developer/API, internal
  • Automated generation — release_notes_generator.py groups entries, formats markdown/JSON, and flags technical language for rewrite

Clarify First

Before generating the release notes, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Audience — B2B/enterprise, consumer, developer/API, or internal (sets the entire tone matrix and how much detail to include)
  • Source changes — the tickets/PRs/changelog to translate, classified into the 5 categories (nothing generates without these)
  • Breaking changes & deprecations — what changed, the required action, and by when (forces the mandatory breaking-change fields that protect user trust)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

bash
python scripts/release_notes_generator.py --input changes.json --product-name "Acme App" --version "2.5.0"
python scripts/release_notes_generator.py --demo --product-name "Acme App" --version "1.0.0"

Include only categories that have entries. Breaking changes must state what changed, what the user must do, and by when. See the references for the full methodology, output template, and flag reference.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/methodology-and-tooling.md — full 5-step methodology, classification tables, rewriting before/after examples, audience tone matrix, output template, troubleshooting, success criteria, and the release_notes_generator.py flag + JSON-schema reference. Read when producing notes or running the tool.
  • references/release-notes-guide.md — best-practices guide on category definitions, audience guidance, and worked examples. Read for the deeper rationale.
  • references/red-flags.md — concrete bad-vs-good entry examples and how to fix them. Read before publishing a draft.
  • assets/release_notes_template.md — ready-to-use release notes document template.
Show full SKILL.md (248 more words)Show less

Integration Points

IntegrationDirectionDescription
sprint-retrospective/Receives fromSprint commit data and type distribution inform what changes to include
senior-pm/ComplementsStakeholder communication plans guide release note audience and tone
execution/create-prd/Receives fromPRD feature descriptions (Section 7) become release note entry drafts
scrum-master/Receives fromSprint review outputs identify what shipped and needs documentation
summarize-meeting/Receives fromRelease planning meeting summaries capture context for release notes
job-stories/ / wwas/Receives fromUser story descriptions inform user-benefit framing of entries

Scope & Limitations

In Scope:

  • Structured release note generation from JSON input with 5 entry categories
  • Automatic technical language detection with rewriting suggestions
  • Markdown and JSON output formatting with category grouping
  • Audience tone guidance (B2B, consumer, developer, internal)
  • Classification rules for New Features, Improvements, Bug Fixes, Breaking Changes, and Deprecations

Out of Scope:

  • Automatic extraction of changes from git history (see sprint-retrospective/ for git analysis)
  • Jira/Linear ticket integration for pulling completed stories (manual JSON input required)
  • Changelog maintenance across multiple releases (this tool generates per-release notes)
  • Distribution to email, in-app, or documentation channels (output is markdown/JSON for further processing)

Important Caveats:

  • The rewriting suggestions are pattern-based heuristics. They catch common technical language but cannot assess whether a description truly communicates user benefit.
  • Semantic versioning alignment is the user's responsibility. The tool does not validate that version numbers follow semver conventions relative to the change types present.
  • Breaking changes require special care. Always include: what changed, what the user must do, and by when. Vague breaking change notes erode user trust.

© borghei, 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 6 other files (scripts, references, assets) in project-management/execution/release-notes of borghei/Claude-Skills.

  • SKILL.md
  • assets/release_notes_template.md
  • examples/wayfinder-v2-1-release-notes.md
  • references/methodology-and-tooling.md
  • references/red-flags.md
  • references/release-notes-guide.md
  • scripts/release_notes_generator.py

Open the folder on GitHubat commit c9a1487

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.

Release Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Notes this skillborghei/Claude-Skills874—~1.5kAutomated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole69k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    69k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • 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.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from borghei/Claude-Skills

All 364 skills in this repo

  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    874 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed

  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    874 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    874 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    874 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    874 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    874 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Release Notes

What does Release Notes do?

Structured release notes that translate technical changes (tickets, changelogs, git logs, PRDs) into user-benefit communication. Release Notes is an agent skill from borghei/Claude-Skills. Structured release notes that translate technical changes (tickets, changelogs, git logs, PRDs) into user-benefit communication.

When should I use Release Notes?

Release Notes fits situations like: product releases; changelog maintenance; customer release announcements.

How do I install Release Notes in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill release-notes -a claude-code`. Or copy the skill folder (project-management/execution/release-notes in borghei/Claude-Skills) 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 borghei/Claude-Skills --skill release-notes -a codex`. Or copy the skill folder (project-management/execution/release-notes in borghei/Claude-Skills) 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 borghei/Claude-Skills --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 Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Release Notes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

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. Its references folder adds about 6.1k tokens, read only when the agent opens those files.

What are the alternatives to Release Notes?

Skills that share tags, products or a category with Release Notes: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 69k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Notes?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.