Agent skill

Release Notes

Generate consistent, well-structured release notes from git history.

MITAuto-check passedDevelopment

Install Release Notes

skills CLI

$ npx skills add OpenHands/extensions --skill release-notes -a claude-code

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

GitHub CLI

$ gh skill install OpenHands/extensions 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/OpenHands/extensions.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/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/

Paste into Claude Code

Install the "release-notes" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/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

$skill-installer install https://github.com/OpenHands/extensions/tree/main/plugins/release-notes

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

skills CLI

$ npx skills add OpenHands/extensions --skill release-notes -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions release-notes --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/release-notes .agents/skills/release-notes && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release-notes" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/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.

skills CLI

$ npx skills add OpenHands/extensions --skill release-notes -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions release-notes --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/release-notes .cursor/skills/release-notes && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release-notes" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/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

$ gemini skills install https://github.com/OpenHands/extensions.git --path plugins/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.

skills CLI

$ npx skills add OpenHands/extensions --skill release-notes -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions release-notes --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/release-notes .gemini/skills/release-notes && rm -rf skills-src

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

Paste into Gemini CLI

Install the "release-notes" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/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.

GitHub CLI

$ gh skill install OpenHands/extensions release-notes

Installs 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).

skills CLI

$ npx skills add OpenHands/extensions --skill release-notes -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/release-notes .github/skills/release-notes && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "release-notes" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/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.

skills CLI

$ npx skills add OpenHands/extensions --skill release-notes -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install OpenHands/extensions release-notes --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/OpenHands/extensions.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/release-notes .opencode/skills/release-notes && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release-notes" agent skill from https://github.com/OpenHands/extensions/tree/main/plugins/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: 157
Token cost: ~964 tokens
SKILL.md length: 306 words
Files: 13 (incl. scripts)
Skills in repo: 78
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate consistent, well-structured release notes from git history.

Works in 2 steps: Conventional commit prefixes: feat:,… → PR labels: breaking-change, bug,…
Tasks that involve Changelog and release notes
SKILL.md covers Features, Quick Start, Release Notes Format and Change Categorization, plus 1 more section
Runs Python scripts from its folder; calls curl; reaches github.com

What it does

Release Notes is an agent skill from OpenHands/extensions. Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including scripts (for example `.plugin/plugin.json`, `README.md` and `action.yml`).

It sits in Development, covering Changelog and release notes. It works with GitHub. The repository describes itself as: Public registry for OpenHands extensions. The licence is MIT.

When your agent uses it

Tasks that involve Changelog and release notes

Example prompts

“/release-notes”

Requirements

Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Conventional commit prefixes: feat:, fix:, docs:, chore:, BREAKING
PR labels: breaking-change, bug, enhancement, documentation

What it can do on your machine

Read from SKILL.md and the folder at commit d008b81. 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 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- curl
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:
- github.com
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 964 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 306 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~61
When it runs · the whole SKILL.md, loaded when a task matches: ~964

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 OpenHands/extensions at commit d008b81, republished under its MIT licence (© OpenHands). 306 words, ~964 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.

name: release-notes
description: Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v*.*.*) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
triggers: /release-notes

Release Notes Generator Plugin

Automates the generation of standardized release notes for OpenHands repositories using an OpenHands agent. The agent reviews the release range, judges significance, groups related PRs, and produces concise markdown for GitHub releases or changelogs.

Features

Automatic tag detection: Finds the previous release tag to determine the commit range
Agent-based editing: Lets the agent decide which changes matter, open with a short conversational summary, and group related PRs into higher-signal summaries while keeping toolkit-maintainer-only details out of the main sections unless they are unusually significant
Structured GitHub context: Supplies PR titles, labels, descriptions, and contributor metadata to guide the agent
Contributor attribution: Includes PR numbers and author usernames for each change
Attribution validation: Verifies every change bullet contains explicit PR/commit references and the matching author handles
Full coverage appendix: Appends a compact ### 🔎 Small Fixes/Internal Changes section grouped by author when needed so every PR and author in the release range is still listed somewhere in the final markdown
New contributor highlighting: Identifies first-time human contributors from merged PR history and excludes bot accounts
Flexible output: Can update GitHub release notes or generate CHANGELOG.md entries

Quick Start

As a GitHub Action

Copy the workflow file to your repository:

bash

mkdir -p .github/workflows
curl -o .github/workflows/release-notes.yml \
  https://raw.githubusercontent.com/OpenHands/extensions/main/plugins/release-notes/workflows/release-notes.yml

PowerShell equivalent:

powershell

New-Item -ItemType Directory -Force .github\workflows | Out-Null
Invoke-WebRequest `
  -Uri https://raw.githubusercontent.com/OpenHands/extensions/main/plugins/release-notes/workflows/release-notes.yml `
  -OutFile .github\workflows\release-notes.yml

Configure required secrets (see the README for details).

Manual Invocation

Use the /release-notes trigger in an OpenHands conversation to generate release notes for the current repository.

Release Notes Format

Generated release notes follow this structure:

markdown

## [v1.2.0] - 2026-03-06

### ⚠️ Breaking Changes
- Remove deprecated `--legacy` CLI flag (#456) @maintainer

### ✨ New Features
- Add support for Claude Sonnet 4.6 model (#445) @contributor1

### 🐛 Bug Fixes
- Fix WebSocket reconnection on network interruption (#451) @contributor3

### 📚 Documentation
- Update installation guide (#442) @contributor2

### 👥 New Contributors
- @contributor3 made their first contribution in #451

**Full Changelog**: https://github.com/org/repo/compare/v1.1.0...v1.2.0

Change Categorization

Changes are categorized based on:

Conventional commit prefixes: feat:, fix:, docs:, chore:, BREAKING:
PR labels: breaking-change, bug, enhancement, documentation

Category	Commit Prefixes	PR Labels
Breaking Changes	`BREAKING:`, `!:` suffix	`breaking-change`, `breaking`
Features	`feat:`, `feature:`	`enhancement`, `feature`
Bug Fixes	`fix:`, `bugfix:`	`bug`, `bugfix`
Documentation	`docs:`	`documentation`, `docs`
Internal	`chore:`, `ci:`, `refactor:`, `test:`	`internal`, `chore`, `ci`

Configuration

See the README for full configuration options and workflow setup instructions.

Files

SKILL.md and 12 other files (scripts) in plugins/release-notes of OpenHands/extensions.

SKILL.md
.claude-plugin
.codex-plugin
.plugin/plugin.json
README.md
action.yml
commands/release-notes.md
scripts/agent_script.py
scripts/generate_release_notes.py
scripts/prompt.py
scripts/validate_release_notes.py
skills/release-notes
workflows/release-notes.yml

Open the folder on GitHubat commit d008b81

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Notes this skillOpenHands/extensions	157	—	~964	Automated safety check: Pass	MIT	today
Cutting A ReleaseTriliumNext/Trilium	38k	—	~3.2k	Automated safety check: Pass	AGPL-3.0	today
Mole CLI Release Flowtw93/Mole	69k	—	~2.5k	Automated safety check: Pass	GPL-3.0	today
Draft Release Notesjamiepine/voicebox	57k	—	~941	Automated safety check: Pass	MIT	today
Mole Release Notes Publishertw93/Mole	69k	—	~1.9k	Automated safety check: Pass	GPL-3.0	today
Release Bumpjamiepine/voicebox	57k	—	~1.1k	Automated safety check: Pass	MIT	today

Similar skills

Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
69k GitHub stars~2.5k tokensUpdated today
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 today
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 today
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 today
DevelopmentAuto-check passed
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
2.7k GitHub stars~2k tokensUpdated 1 mo ago
DevelopmentAuto-check passed

Questions about Release Notes

What does Release Notes do?

Generate consistent, well-structured release notes from git history. Release Notes is an agent skill from OpenHands/extensions. Generate consistent, well-structured release notes from git history.

When should I use Release Notes?

Release Notes fits situations like: tasks that involve Changelog and release notes.

How do I install Release Notes in Claude Code?

Run `npx skills add OpenHands/extensions --skill release-notes -a claude-code`. Or copy the skill folder (plugins/release-notes in OpenHands/extensions) 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 OpenHands/extensions --skill release-notes -a codex`. Or copy the skill folder (plugins/release-notes in OpenHands/extensions) 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 OpenHands/extensions --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 (curl). Our summary lists: Python 3.

Does Release Notes access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it 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. 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 (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Notes use?

About 964 tokens (SKILL.md is roughly 3.9k 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: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 69k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Notes?

OpenHands (a GitHub organization) maintains it in OpenHands/extensions, which has 157 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 6, 2026.

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

Install Release Notes

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Release Notes Generator Plugin

Features

Quick Start

As a GitHub Action

Manual Invocation

Release Notes Format

Change Categorization

Configuration

Files

Compare with similar skills

Similar skills

More from OpenHands/extensions

Related

Questions about Release Notes