Release Changelog
VoidenHQ/voiden
A skill your agent uses whenever asked to write/create a new changelog entry for a new Voiden app version (e.g.
Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.
Install Release Generate Release Notes
$ npx skills add mountain-loop/yaak --skill release-generate-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mountain-loop/yaak release-generate-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/mountain-loop/yaak.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-generate-release-notes .claude/skills/release-generate-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-generate-release-notes" agent skill from https://github.com/mountain-loop/yaak/tree/main/.codex/skills/release-generate-release-notes into .claude/skills/release-generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-generate-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/mountain-loop/yaak/tree/main/.codex/skills/release-generate-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 mountain-loop/yaak --skill release-generate-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mountain-loop/yaak release-generate-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mountain-loop/yaak.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/release-generate-release-notes .agents/skills/release-generate-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-generate-release-notes" agent skill from https://github.com/mountain-loop/yaak/tree/main/.codex/skills/release-generate-release-notes into .agents/skills/release-generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-generate-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 mountain-loop/yaak --skill release-generate-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mountain-loop/yaak release-generate-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mountain-loop/yaak.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/release-generate-release-notes .cursor/skills/release-generate-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-generate-release-notes" agent skill from https://github.com/mountain-loop/yaak/tree/main/.codex/skills/release-generate-release-notes into .cursor/skills/release-generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-generate-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/mountain-loop/yaak.git --path .codex/skills/release-generate-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 mountain-loop/yaak --skill release-generate-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mountain-loop/yaak release-generate-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mountain-loop/yaak.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/release-generate-release-notes .gemini/skills/release-generate-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-generate-release-notes" agent skill from https://github.com/mountain-loop/yaak/tree/main/.codex/skills/release-generate-release-notes into .gemini/skills/release-generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-generate-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 mountain-loop/yaak release-generate-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 mountain-loop/yaak --skill release-generate-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mountain-loop/yaak.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/release-generate-release-notes .github/skills/release-generate-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-generate-release-notes" agent skill from https://github.com/mountain-loop/yaak/tree/main/.codex/skills/release-generate-release-notes into .github/skills/release-generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-generate-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 mountain-loop/yaak --skill release-generate-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 mountain-loop/yaak release-generate-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mountain-loop/yaak.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/release-generate-release-notes .opencode/skills/release-generate-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-generate-release-notes" agent skill from https://github.com/mountain-loop/yaak/tree/main/.codex/skills/release-generate-release-notes into .opencode/skills/release-generate-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-generate-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-generate-release-notes- GitHub stars
- 19k
- Token cost
- ~548 tokens
- SKILL.md length
- 254 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.
- Works in 6 steps: Determine target tag. → Determine previous comparable tag → Collect commits in range → …
- Replace the old Claude generate-release-notes command
- SKILL.md covers Workflow, Formatting Rules and Release Creation Prompt
- Calls gh and git; reaches github.com
What it does
Release Generate Release Notes is an agent skill from mountain-loop/yaak. Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Use when asked to run or replace the old Claude generate-release-notes command.
Its SKILL.md is about 550 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 gRPC, Postman, Tauri and GraphQL. The repository describes itself as: The most intuitive desktop API client. Organize and execute REST, GraphQL, WebSockets, Server Sent Events, and gRPC 🦬. The licence is MIT.
When your agent uses it
- Replace the old Claude generate-release-notes command
- Tasks that involve Changelog and release notes
Example prompts
- “/release-generate-release-notes”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Determine target tag.
- Determine previous comparable tag
- Collect commits in range
- For linked PRs, fetch metadata
- Extract useful details
- Format notes using Yaak style
What it can do on your machine
Read from SKILL.md and the folder at commit 919e58f. 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
Shell commands in SKILL.md call:
ghgit
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 Generate Release Notes loads about 548 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 254 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 mountain-loop/yaak at commit 919e58f, republished under its MIT licence (© mountain-loop). 254 words, ~548 tokens.
Download SKILL.mdSave it as
.claude/skills/release-generate-release-notes/SKILL.md (or your agent's skills folder).- name
- release-generate-release-notes
- description
- Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Use when asked to run or replace the old Claude generate-release-notes command.
Generate Release Notes
Generate formatted markdown release notes for a Yaak tag.
Workflow
- Determine target tag.
- Determine previous comparable tag:
- Beta tag: compare against previous beta (if the root version is the same) or stable tag.
- Stable tag: compare against previous stable tag.
- Collect commits in range:
git log --oneline <prev_tag>..<target_tag>
- For linked PRs, fetch metadata:
gh pr view <PR_NUMBER> --json number,title,body,author,url
- Extract useful details:
- Feedback URLs (
feedback.yaak.app) - Contributor GitHub handles from
author.login - Plugin install links or other notable context
- Feedback URLs (
- Format notes using Yaak style:
- Changelog badge at top
- Bulleted items with PR links where available
- Contributor handles for external PRs
- Feedback links where available
- Full changelog compare link at bottom
Formatting Rules
- Wrap final notes in a markdown code fence.
- Keep a blank line before and after the code fence.
- Output the markdown code block last.
- Append contributor attribution to PR-backed bullets for non-
@gschierauthors, usingby [@handle](https://github.com/handle). - Do not append
by @gschierfor PRs authored by@gschier. - These are app release notes. Exclude CLI-only changes (commits prefixed with
cli:or only touchingcrates-cli/) since the CLI has its own release process.
Release Creation Prompt
After producing notes, ask whether to create a draft GitHub release.
If confirmed and release does not yet exist, run:
gh release create <tag> --draft --prerelease --title "Release <version_without_v>" --notes '<release notes>'
If a draft release for the tag already exists, update it instead:
gh release edit <tag> --title "Release <version_without_v>" --notes-file <path_to_notes>
Use title format Release <version_without_v>, e.g. v2026.2.1-beta.1 -> Release 2026.2.1-beta.1.
© mountain-loop, 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 .codex/skills/release-generate-release-notes of mountain-loop/yaak.
Open the folder on GitHubat commit 919e58f
Compare with similar skills
Release Generate 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 Generate Release Notes this skillmountain-loop/yaak | 19k | — | ~548 | Automated safety check: Pass | MIT | |
| Release ChangelogVoidenHQ/voiden | 1.9k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Release WorkflowGoldziher/spikard | 123 | — | ~909 | Automated safety check: Pass | MIT | |
| Plugin Release CheckVoidenHQ/voiden | 1.9k | — | ~857 | Automated safety check: Pass | Apache-2.0 | |
| Cline Desktop App Releasecline/cline | 70k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Cut Releasedelexw/claude-code-trace | 376 | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Release Workflow
Goldziher/spikard
Release/publish the spikard Rust core crate and CLI end-to-end.
Plugin Release Check
VoidenHQ/voiden
A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.
Cline Desktop App Release
cline/cline
Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.
Cut Release
delexw/claude-code-trace
Cuts a new versioned release of claude-code-trace end-to-end without asking any questions.
Store Submit
zhitongblog/solomd
Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.
More from mountain-loop/yaak
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
Yaak Changelog
mountain-loop/yaak
Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak.
Related
Categories
Questions about Release Generate Release Notes
What does Release Generate Release Notes do?
Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Release Generate Release Notes is an agent skill from mountain-loop/yaak. Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.
When should I use Release Generate Release Notes?
Release Generate Release Notes fits situations like: replace the old Claude generate-release-notes command; tasks that involve Changelog and release notes.
How do I install Release Generate Release Notes in Claude Code?
Run `npx skills add mountain-loop/yaak --skill release-generate-release-notes -a claude-code`. Or copy the skill folder (.codex/skills/release-generate-release-notes in mountain-loop/yaak) into .claude/skills/release-generate-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Release Generate Release Notes in Codex?
Run `npx skills add mountain-loop/yaak --skill release-generate-release-notes -a codex`. Or copy the skill folder (.codex/skills/release-generate-release-notes in mountain-loop/yaak) into .agents/skills/release-generate-release-notes in your project. Codex loads it when a task matches its description.
Can I use Release Generate 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 mountain-loop/yaak --skill release-generate-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-generate-release-notes, .gemini/skills/release-generate-release-notes, .github/skills/release-generate-release-notes and .opencode/skills/release-generate-release-notes in your project.
What does Release Generate Release Notes need to run?
Going by SKILL.md and its folder, Release Generate Release Notes needs the command-line tools its instructions call (gh and git).
Does Release Generate 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 Generate 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 Generate Release Notes use?
Release Generate 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 Generate Release Notes use?
About 548 tokens (SKILL.md is roughly 2.2k 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 Generate Release Notes?
Skills that share tags, products or a category with Release Generate Release Notes: Release Changelog (VoidenHQ/voiden, 1.9k stars), Release Workflow (Goldziher/spikard, 123 stars), Plugin Release Check (VoidenHQ/voiden, 1.9k stars) and Cline Desktop App Release (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Generate Release Notes?
mountain-loop (a GitHub organization) maintains it in mountain-loop/yaak, which has 19,294 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: mountain-loop/yaak on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.