Why
Sma1lboy/rove
A skill your agent uses for 'why does X work this way', 'why we picked Y', '为什么这么设计', design rationale, regressions, or where a magic number came from.
Generate a CHANGELOG.md entry from git history since the last tag, categorized by type (features, fixes, security, breaking changes).
Install Release Notes
$ npx skills add GlitterKill/sdl-mcp --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GlitterKill/sdl-mcp 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/GlitterKill/sdl-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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 GlitterKill/sdl-mcp --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GlitterKill/sdl-mcp release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GlitterKill/sdl-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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 GlitterKill/sdl-mcp --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GlitterKill/sdl-mcp release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GlitterKill/sdl-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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/GlitterKill/sdl-mcp.git --path .codex/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 GlitterKill/sdl-mcp --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GlitterKill/sdl-mcp release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GlitterKill/sdl-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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 GlitterKill/sdl-mcp 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 GlitterKill/sdl-mcp --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GlitterKill/sdl-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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 GlitterKill/sdl-mcp --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 GlitterKill/sdl-mcp release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GlitterKill/sdl-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/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/GlitterKill/sdl-mcp/tree/main/.codex/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
- 490
- Token cost
- ~925 tokens
- SKILL.md length
- 375 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Generate a CHANGELOG.md entry from git history since the last tag, categorized by type (features, fixes, security, breaking changes).
- Works in 9 steps: Set the release identities → Read the complete history → Categorize every commit into these… → …
- Tasks that involve Changelog and release notes
- SKILL.md covers Steps and Rules
- Calls git, npm and node
What it does
Release Notes is an agent skill from GlitterKill/sdl-mcp. Generate a CHANGELOG.md entry from git history since the last tag, categorized by type (features, fixes, security, breaking changes). Matches the existing CHANGELOG format.
Its SKILL.md is about 930 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 and Git workflow. It works with Model Context Protocol. The repository describes itself as: Symbol Delta Ledger (SDL-MCP) is a policy-centered context budget layer for coding agents: Symbol-graph intelligence combined with precision tools. It turns sprawling codebases…
When your agent uses it
- Tasks that involve Changelog and release notes
- Tasks that involve Git workflow
Example prompts
- “/release-notes”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Set the release identities
- Read the complete history
- Categorize every commit into these sections, matching the existing CHANGELOG.md style
- Draft concise, grouped summaries
- Present the CHANGELOG draft for review
- Validate before the expensive release checks
- Create the release commit and annotated tag
- Build release notes from the tagged target
- Publish the generated file
What it can do on your machine
Read from SKILL.md and the folder at commit 383bbda. 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:
gitnpmnodegh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npm and gh, which can reach the network depending on how they are called.
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 925 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 375 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 375 words (~925 tokens).
“Generate a CHANGELOG entry for the next release by analyzing the complete release range and preserving its validated target through publication.”
- name
- release-notes
- disable-model-invocation
- true
Files
Just SKILL.md in .codex/skills/release-notes of GlitterKill/sdl-mcp.
Open the folder on GitHubat commit 383bbda
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 skillGlitterKill/sdl-mcp | 490 | — | ~925 | Automated safety check: Pass | Custom licence | |
| WhySma1lboy/rove | 146 | — | ~5.6k | Automated safety check: Pass | MIT | |
| ReleasePrefectHQ/fastmcp | 28k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Go-Redis Release Preparationredis/go-redis | 22k | — | ~1.1k | Automated safety check: Pass | BSD-2-Clause |
Similar skills
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
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.
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.
- Official
Go-Redis Release Preparation
redis/go-redis
Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
More from GlitterKill/sdl-mcp
Test Scope
GlitterKill/sdl-mcp
Determine which test suites are affected by recent code changes and run only the relevant ones.
Related
Works with
Categories
Questions about Release Notes
What does Release Notes do?
Generate a CHANGELOG.md entry from git history since the last tag, categorized by type (features, fixes, security, breaking changes). Release Notes is an agent skill from GlitterKill/sdl-mcp.md entry from git history since the last tag, categorized by type (features, fixes, security, breaking changes).
When should I use Release Notes?
Release Notes fits situations like: tasks that involve Changelog and release notes; tasks that involve Git workflow.
How do I install Release Notes in Claude Code?
Run `npx skills add GlitterKill/sdl-mcp --skill release-notes -a claude-code`. Or copy the skill folder (.codex/skills/release-notes in GlitterKill/sdl-mcp) 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 GlitterKill/sdl-mcp --skill release-notes -a codex`. Or copy the skill folder (.codex/skills/release-notes in GlitterKill/sdl-mcp) 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 GlitterKill/sdl-mcp --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 the command-line tools its instructions call (git, npm, node and gh).
Does Release Notes access the network?
SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. 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 has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Release Notes use?
About 925 tokens (SKILL.md is roughly 3.7k 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: Why (Sma1lboy/rove, 146 stars), Release (PrefectHQ/fastmcp, 28k stars), Release Bump (jamiepine/voicebox, 57k stars) and Git Workflow and Versioning (addyosmani/agent-skills, 102k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
GlitterKill (a GitHub user) maintains it in GlitterKill/sdl-mcp, which has 490 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 21, 2026.
Source: GlitterKill/sdl-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.