New: 98,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

Git Changelog

by diodeme in diodeme/Gold-Band

Create and localize user-facing release notes from an explicit Git change range.

AGPL-3.0Auto-check passedDevelopment

Install Git Changelog

skills CLI
$ npx skills add diodeme/Gold-Band --skill git-changelog -a claude-code

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

GitHub CLI
$ gh skill install diodeme/Gold-Band git-changelog --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/diodeme/Gold-Band.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/git-changelog .claude/skills/git-changelog && 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
git-changelog
GitHub stars
143
Token cost
~1.4k tokens
SKILL.md length
656 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Create and localize user-facing release notes from an explicit Git change range.

  • Works in 7 steps: Read the Release PR, release-please… → Draft the user-facing Simplified Chinese… → Keep the historical structure and tone:… → …
  • The user asks for a changelog
  • SKILL.md covers Confirm release inputs first, Prepare the release notes and Release metadata and generator…
  • Reaches static.dion.blue

What it does

Git Changelog is an agent skill from diodeme/Gold-Band. Create and localize user-facing release notes from an explicit Git change range. Use when the user asks for a changelog, release notes, multilingual update notes, or GitHub Release copy. Require explicit start and end points, a target release version, and the user's normal or critical update choice; ask for missing inputs before proceeding.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Changelog and release notes and Git workflow. It works with Git and GitHub. The repository describes itself as: Desktop app for harness engineering, loop engineering, graph engineering—and whatever comes next in local AI-agent workflows. The licence is AGPL-3.0.

When your agent uses it

  • The user asks for a changelog
  • Multilingual update notes
  • GitHub Release copy

Example prompts

  • “/git-changelog”

Workflow steps

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

  1. Read the Release PR, release-please CHANGELOG.md, merged PRs and commits in the range, and relevant product documents.
  2. Draft the user-facing Simplified Chinese release notes. Use release-notes/0.15.0/zh-CN.md through release-notes/0.17.0/zh-CN.md as style…
  3. Keep the historical structure and tone: ## 功能新增/调整, ## 体验优化, numbered feature headings, short workflow steps, explicit limitations, and >…
  4. Include only verified user-visible changes. Do not invent details from commit titles alone. Remove duplicates and internal-only…
  5. Use stable https://static.dion.blue/... image URLs. Check supplied images and links when network access is available; do not rewrite…
  6. Translate the confirmed Chinese source into zh-TW, en, ja-JP, ko-KR, pt-BR, and es. Preserve facts, Markdown structure, URLs, warnings…
  7. Review every language against zh-CN for omissions, inconsistent facts, or fabricated content.

What it can do on your machine

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

    Hosts in commands or code, which the agent is likely to contact:

    • static.dion.blue

    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

Git Changelog loads about 1.4k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 656 words of instructions outside code blocks.

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

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 diodeme/Gold-Band at commit 75622ac, republished under its AGPL-3.0 licence (© diodeme). 656 words, ~1,350 tokens.

Download SKILL.mdSave it as .claude/skills/git-changelog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
git-changelog
description
Create and localize user-facing release notes from an explicit Git change range. Use when the user asks for a changelog, release notes, multilingual update notes, or GitHub Release copy. Require explicit start and end points, a target release version, and the user's normal or critical update choice; ask for missing inputs before proceeding.

Git Changelog

Confirm release inputs first

Require both a changelog start point and end point. Accept tags, commits, SHAs, branches, dates, or another unambiguous Git range.

Also require an explicit target release version and the user's choice of normal (critical: false) or critical (critical: true) update for that version. Reuse a clear answer already given for this target version; do not ask again unnecessarily. If any input is missing or ambiguous, ask the user and wait. Do not infer range boundaries or the target version from the latest tag, the previous release, the current branch, or HEAD. Never infer criticality from commits, commit labels, breaking changes, security fixes, or release-note wording.

Explain the choice when asking:

  • Normal update: notify the user and wait for a manual update action; no automatic download or installation.
  • Critical update: download the signed package in the background and install through the normal application exit lifecycle (or the existing subsequent-startup pending-install path). Do not force an immediate restart or interrupt active work merely because a critical update is discovered or finishes downloading.

Before overwriting any existing target-version file, read it. Inspect an existing release-notes/<version>/release.json and compare it with the user's explicit choice; the file alone is not user confirmation. Resolve conflicts or ambiguous instructions with the user rather than silently replacing the choice.

Prepare the release notes

  1. Read the Release PR, release-please CHANGELOG.md, merged PRs and commits in the range, and relevant product documents.
  2. Draft the user-facing Simplified Chinese release notes. Use release-notes/0.15.0/zh-CN.md through release-notes/0.17.0/zh-CN.md as style references.
  3. Keep the historical structure and tone: ## 功能新增/调整, ## 体验优化, numbered feature headings, short workflow steps, explicit limitations, and > [!attention] callouts when needed.
  4. Include only verified user-visible changes. Do not invent details from commit titles alone. Remove duplicates and internal-only implementation details.
  5. Use stable https://static.dion.blue/... image URLs. Check supplied images and links when network access is available; do not rewrite images to GitHub asset URLs.
  6. Translate the confirmed Chinese source into zh-TW, en, ja-JP, ko-KR, pt-BR, and es. Preserve facts, Markdown structure, URLs, warnings, code, identifiers, and product terms.
  7. Review every language against zh-CN for omissions, inconsistent facts, or fabricated content.

Write files to:

text
release-notes/<version>/zh-CN.md
release-notes/<version>/zh-TW.md
release-notes/<version>/en.md
release-notes/<version>/ja-JP.md
release-notes/<version>/ko-KR.md
release-notes/<version>/pt-BR.md
release-notes/<version>/es.md
release-notes/<version>/release.json

Always write release.json alongside all seven locale files, including for a normal update. Its complete JSON object must be exactly {"critical": false} or {"critical": true}, matching the confirmed choice: one boolean field, no additional keys. Report the target version, final normal/critical choice, and files written in the completion summary.

Show full SKILL.md (246 more words)Show less

Release metadata and generator contract

release-notes/<version>/release.json is the version-scoped source of truth for default-channel criticality; the generated manifests are projections, not independent choices. The generator reads metadata from the release source SHA/tag, not an unrelated workflow branch or an uncommitted working tree. All seven locale files and release.json must be included in that release SHA/tag before generation and publication; merely creating the files locally is insufficient.

  • Missing release.json means a normal historical release (critical: false); this historical default does not permit this skill to omit the file for a newly prepared release.
  • A present file must parse as a JSON object containing exactly critical with a boolean value. Malformed JSON, missing fields, non-boolean values, arrays/null, or extra keys are invalid; fail before writing any generated output, rather than falling back to normal or leaving partial output.
  • All eight default manifests (seven latest.<locale>.json plus latest.json) must reflect the same choice: include critical: true for a critical release; omit the field for a normal release. latest.json remains identical to the Simplified Chinese manifest.

GitHub Release uses the Chinese and English files. The default client channel uses all seven languages. The wb channel remains a single latest.json; its existing build/critical controls are unchanged and do not consume this default-channel metadata. Keep CHANGELOG.md managed by release-please.

Do not automatically commit, push, tag, or publish a GitHub Release. The requirement to include these files in the release SHA/tag is not authorization to do so; each action requires a separate user request.

© diodeme, AGPL-3.0. 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 1 other file in .agents/skills/git-changelog of diodeme/Gold-Band.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 75622ac

Compare with similar skills

Git Changelog 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.

Git Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Changelog this skilldiodeme/Gold-Band143—~1.4kAutomated safety check: PassAGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
Hunk Release Workflowmodem-dev/hunk9.5k—~3.8kAutomated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9k—~6.9kAutomated safety check: PassCustom licence
pybind11 Release Publicationpybind/pybind1118k—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • 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

  • Go-Redis Release Preparation

    redis/go-redis

    Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

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

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

    9.5k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed

  • pybind11 Release Publication

    pybind/pybind11

    Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.

    18k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Obot Release Notes Drafter

    obot-platform/obot

    Drafts release notes for an upcoming Obot minor release and saves them as an unpublished GitHub draft release, never tagging or publishing.

    1.1k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

More from diodeme/Gold-Band

All 11 skills in this repo

  • Rust Async Patterns

    diodeme/Gold-Band

    Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns.

    143 GitHub starsUsed in 10 repos~3.1k tokens
    Auto-check passed

  • Rust Profiling

    diodeme/Gold-Band

    Rust profiling skill for performance analysis. An agent skill from diodeme/Gold-Band.

    143 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check: notes

  • Memory Leak Debugging

    diodeme/Gold-Band

    Diagnoses and resolves memory leaks in JavaScript/Node.js applications.

    143 GitHub stars~712 tokensUpdated 8 days ago
    Auto-check passed

  • Git PR

    diodeme/Gold-Band

    Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR…

    143 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed

  • Stitch Design

    diodeme/Gold-Band

    Unified entry point for Stitch design work. An agent skill from diodeme/Gold-Band.

    143 GitHub starsUsed in 1 repo~925 tokens
    Auto-check passed

  • Memory Leak Audit

    diodeme/Gold-Band

    Audit code for memory leaks and disposable issues. An agent skill from diodeme/Gold-Band.

    143 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Git Changelog

What does Git Changelog do?

Create and localize user-facing release notes from an explicit Git change range. Git Changelog is an agent skill from diodeme/Gold-Band. Create and localize user-facing release notes from an explicit Git change range.

When should I use Git Changelog?

Git Changelog fits situations like: the user asks for a changelog; multilingual update notes; GitHub Release copy.

How do I install Git Changelog in Claude Code?

Run `npx skills add diodeme/Gold-Band --skill git-changelog -a claude-code`. Or copy the skill folder (.agents/skills/git-changelog in diodeme/Gold-Band) into .claude/skills/git-changelog in your project. Claude Code loads it when a task matches its description.

How do I install Git Changelog in Codex?

Run `npx skills add diodeme/Gold-Band --skill git-changelog -a codex`. Or copy the skill folder (.agents/skills/git-changelog in diodeme/Gold-Band) into .agents/skills/git-changelog in your project. Codex loads it when a task matches its description.

Can I use Git Changelog 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 diodeme/Gold-Band --skill git-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-changelog, .gemini/skills/git-changelog, .github/skills/git-changelog and .opencode/skills/git-changelog in your project.

What does Git Changelog need to run?

SKILL.md names no scripts, command-line tools or credentials: Git Changelog is instructions for the agent only.

Does Git Changelog access the network?

SKILL.md names 1 domain. In commands or code: static.dion.blue; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Git Changelog 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 Git Changelog use?

Git Changelog is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Changelog use?

About 1.4k tokens (SKILL.md is roughly 5.4k 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 Git Changelog?

Skills that share tags, products or a category with Git Changelog: Release Bump (jamiepine/voicebox, 57k stars), Go-Redis Release Preparation (redis/go-redis, 22k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars) and Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Changelog?

diodeme (a GitHub user) maintains it in diodeme/Gold-Band, which has 143 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 30, 2026.

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