Generate Release Notes
teambit/bit
Generate comprehensive release notes for Bit from git commits and pull requests.
A skill your agent uses when drafting, generating, revising, or reviewing GitHub release notes, changelogs, or a "What's Changed" section for an XYZ release.
Install Release Notes
$ npx skills add GEOLYTIX/xyz --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GEOLYTIX/xyz 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/GEOLYTIX/xyz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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 GEOLYTIX/xyz --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GEOLYTIX/xyz release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GEOLYTIX/xyz.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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 GEOLYTIX/xyz --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GEOLYTIX/xyz release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GEOLYTIX/xyz.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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/GEOLYTIX/xyz.git --path .claude/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 GEOLYTIX/xyz --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GEOLYTIX/xyz release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GEOLYTIX/xyz.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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 GEOLYTIX/xyz 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 GEOLYTIX/xyz --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GEOLYTIX/xyz.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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 GEOLYTIX/xyz --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 GEOLYTIX/xyz release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GEOLYTIX/xyz.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/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/GEOLYTIX/xyz/tree/main/.claude/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
- 133
- Token cost
- ~1.4k tokens
- SKILL.md length
- 768 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting, generating, revising, or reviewing GitHub release notes, changelogs, or a "What's Changed" section for an XYZ release.
- Works in 5 steps: Identify the repository, previous… → Once the candidate pull requests are… → Do not rely on a pull request title when… → …
- Reviewing GitHub release notes
- SKILL.md covers Gather The Changes, Organize The Notes, Write The File and Write Each Entry, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Release Notes is an agent skill from GEOLYTIX/xyz. Use when drafting, generating, revising, or reviewing GitHub release notes, changelogs, or a "What's Changed" section for an XYZ release.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. It works with GitHub, JavaScript and Node.js. The repository describes itself as: An open source javascript framework for spatial data and application interfaces. The licence is MIT.
When your agent uses it
- Reviewing GitHub release notes
- A Whats Changed section for an XYZ release
Example prompts
- “s Changed”
- “/release-notes”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify the repository, previous version, new version, and included pull requests from the user's request or repository context.
- Once the candidate pull requests are identified, research each one with its own subagent rather than fetching pages directly in the main…
- Do not rely on a pull request title when its diff, description, or linked issues provide a clearer or more complete explanation of the…
- Ask one concise clarification question if the release range cannot be determined. Never invent versions, pull request numbers…
- Include user-visible fixes, features, documentation improvements, and meaningful maintenance changes. Exclude merge commits, release…
What it can do on your machine
Read from SKILL.md and the folder at commit 6d3dacc. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
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 1.4k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 768 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 GEOLYTIX/xyz at commit 6d3dacc, republished under its MIT licence (© GEOLYTIX). 768 words, ~1,397 tokens.
Download SKILL.mdSave it as
.claude/skills/release-notes/SKILL.md (or your agent's skills folder).- name
- release-notes
- description
- Use when drafting, generating, revising, or reviewing GitHub release notes, changelogs, or a "What's Changed" section for an XYZ release.
Release Notes
Create concise, user-focused release notes from the supplied pull requests, commits, or version range. Match the XYZ release format below exactly unless the user explicitly requests another format.
Gather The Changes
- Identify the repository, previous version, new version, and included pull requests from the user's request or repository context.
- Once the candidate pull requests are identified, research each one with its own subagent rather than fetching pages directly in the main thread. Launch one subagent per pull request, all in a single message, so they run in parallel — each PR's research is independent of the others. Give each subagent the PR URL and ask it to return, as a compact structured summary (not a raw page dump):
- Title, author, and actual behavior verified from the diff and description — do not rely on the title alone when the diff or description tells a clearer story.
- Every issue linked to the PR (GitHub's "Development" sidebar entries and any "Closes/Fixes/Resolves #" references in the description), with that issue's full title and body fetched separately. A PR description frequently omits scope, sub-problems, or the original motivation that only the linked issue records — treat the PR description as a summary, not the full picture.
- Do not rely on a pull request title when its diff, description, or linked issues provide a clearer or more complete explanation of the change.
- Ask one concise clarification question if the release range cannot be determined. Never invent versions, pull request numbers, contributors, links, behavior, or impact.
- Include user-visible fixes, features, documentation improvements, and meaningful maintenance changes. Exclude merge commits, release preparation commits, and incidental refactors unless they affect users or maintainers in a way worth announcing.
Organize The Notes
Start with ## What's Changed. Group related pull requests under descriptive ### headings in title case, such as Map and Theme Fixes, Filter Fixes, CSV Upload Fixes, or Documentation. Derive headings from the actual changes. Do not force a fixed set of categories. Order sections by user impact and keep closely related changes together. Put documentation and internal maintenance last. Give each pull request its own bullet unless multiple pull requests implement inseparable parts of the same user-facing change. Finish with a bold Full changelog: link comparing the previous and new tags.
Write The File
For drafting, generating, or revising release notes, write the finished Markdown to release-notes/<new-version>.md, preserving the tag exactly, including its leading v. For example, release v4.23.6 must be written to release-notes/v4.23.6.md.
Resolve release-notes/ from the Git workspace root, not from this skill's directory.
Create the release-notes/ directory or version file when it does not exist.
Read an existing version file before editing it. Replace its contents with the finished release notes because the version file is the release artifact; do not append another copy of the notes.
If the user provides an explicit destination file, use that path instead.
When the user asks only for a review, do not edit the file unless they also ask for fixes.
Show full SKILL.md (272 more words)Show less
Write Each Entry
Use this structure:
markdown
- Concise user-visible outcome in the past tense. Explain the previous problem and the corrected behavior in plain language. Thanks @author! #123
Follow these rules:
Begin with a bold sentence that can be understood by someone scanning the release.
Prefer outcomes such as Prevented, Fixed, Improved, Added, or <thing> now <does something> over implementation-led wording.
Explain what went wrong before, when it occurred, and what happens now. Include enough technical detail to make the fix meaningful, but avoid narrating the code diff.
Use backticks for code identifiers, configuration keys, values, filenames, and types.
Use active voice, precise wording, and short paragraphs. Avoid hype, filler, vague claims, and phrases such as "various fixes" or "under the hood".
Preserve important distinctions such as numeric versus integer behavior, clustered versus individual features, or missing versus empty values.
End every entry with the exact attribution and linked pull request form: Thanks @author! #123.
Do not add issue links, commit hashes, test details, or breaking-change labels unless they are relevant and verified.
Output Format
markdown
What's Changed
Category Name
- User-visible outcome. Previous behavior, its impact, and the corrected behavior. Thanks @author! #123
Documentation
- Improved documentation for the affected feature. Explain what is clearer or easier to maintain now. Thanks @author! #456
Full changelog: vPREVIOUS...vNEW Before writing, verify that every included pull request appears once, every attribution and link is correct, headings reflect their entries, and the comparison URL uses the correct tags. After writing, respond with a concise summary and the repository-relative file path instead of repeating the complete release notes, unless the user asks to see them in the response.
© GEOLYTIX, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/release-notes of GEOLYTIX/xyz.
Open the folder on GitHubat commit 6d3dacc
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 skillGEOLYTIX/xyz | 133 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Generate Release Notesteambit/bit | 18k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Release Roundethereumjs/ethereumjs-monorepo | 2.8k | — | ~2k | Automated safety check: Pass | None | |
| Release WorkflowCaldis/react-zmage | 946 | — | ~3.6k | Automated safety check: Notes | MIT | |
| ReleaseOvenMediaLabs/OvenPlayer | 592 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Release TS SDKaptos-labs/aptos-ts-sdk | 116 | — | ~864 | Automated safety check: Pass | Custom licence |
Similar skills
Release Round
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
Release Workflow
Caldis/react-zmage
A skill your agent uses when the user wants to ship a new version of react-zmage to npm.
Release
OvenMediaLabs/OvenPlayer
Release ovenplayer to npm — confirm the version, verify the committed dist/ bundle is current, write the release notes, and open a draft GitHub Release for the user to publish.
Release TS SDK
aptos-labs/aptos-ts-sdk
A skill your agent uses when cutting a release of @aptos-labs/ts-sdk or @aptos-labs/confidential-asset.
Nylas Nodejs Release
nylas/nylas-nodejs
Prepares nylas-nodejs SDK releases on a versioned release branch with CHANGELOG updates, version bump, git tag, and PR body.
More from GEOLYTIX/xyz
Review PR
GEOLYTIX/xyz
A skill your agent uses when reviewing a pull request, a branch, or uncommitted working changes in the XYZ/MAPP repository — whether the user asks to "review this PR", "check my changes before I…
Related
Works with
Categories
Questions about Release Notes
What does Release Notes do?
A skill your agent uses when drafting, generating, revising, or reviewing GitHub release notes, changelogs, or a "What's Changed" section for an XYZ release. Release Notes is an agent skill from GEOLYTIX/xyz. Use when drafting, generating, revising, or reviewing GitHub release notes, changelogs, or a "What's Changed" section for an XYZ release.
When should I use Release Notes?
Release Notes fits situations like: reviewing GitHub release notes; A Whats Changed section for an XYZ release.
How do I install Release Notes in Claude Code?
Run `npx skills add GEOLYTIX/xyz --skill release-notes -a claude-code`. Or copy the skill folder (.claude/skills/release-notes in GEOLYTIX/xyz) 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 GEOLYTIX/xyz --skill release-notes -a codex`. Or copy the skill folder (.claude/skills/release-notes in GEOLYTIX/xyz) 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 GEOLYTIX/xyz --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?
SKILL.md names no scripts, command-line tools or credentials: Release Notes is instructions for the agent only.
Does Release Notes access the network?
SKILL.md names 1 domain. As links in the text: github.com. 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 (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 1.4k tokens (SKILL.md is roughly 5.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: Generate Release Notes (teambit/bit, 18k stars), Release Round (ethereumjs/ethereumjs-monorepo, 2.8k stars), Release Workflow (Caldis/react-zmage, 946 stars) and Release (OvenMediaLabs/OvenPlayer, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
GEOLYTIX (a GitHub organization) maintains it in GEOLYTIX/xyz, which has 133 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: GEOLYTIX/xyz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.