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

Generate Changelog

by timusus in timusus/Shuttle2

Generate a user-facing changelog entry for a new Android release from the unreleased changelog fragments, audited against git commits since the last shipped tag.

Apache-2.0Auto-check passedDevelopment

Install Generate Changelog

skills CLI
$ npx skills add timusus/Shuttle2 --skill generate-changelog -a claude-code

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

GitHub CLI
$ gh skill install timusus/Shuttle2 generate-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/timusus/Shuttle2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/generate-changelog .claude/skills/generate-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
generate-changelog
GitHub stars
229
Token cost
~1.5k tokens
SKILL.md length
749 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate a user-facing changelog entry for a new Android release from the unreleased changelog fragments, audited against git commits since the last shipped tag.

  • Works in 4 steps: Collect the unreleased changes → Generate the changelog entry → Output format → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Inputs and Steps
  • Calls git

What it does

Generate Changelog is an agent skill from timusus/Shuttle2. Generate a user-facing changelog entry for a new Android release from the unreleased changelog fragments, audited against git commits since the last shipped tag. Updates changelog.json and consumes the fragments.

Its SKILL.md is about 1.5k 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 Commit messages. It works with Android. The repository describes itself as: Shuttle Music: a music player for Android and iOS. Plays local files and streams from Jellyfin, Emby, Plex and Navidrome/Subsonic, with Chromecast, Android Auto, EQ and replay… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Commit messages

Example prompts

  • “/generate-changelog”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Collect the unreleased changes
  2. Generate the changelog entry
  3. Output format
  4. Update changelog.json and consume the fragments

What it can do on your machine

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

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Generate Changelog loads about 1.5k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 749 words of instructions outside code blocks.

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

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 timusus/Shuttle2 at commit e05449e, republished under its Apache-2.0 licence (© timusus). 749 words, ~1,543 tokens.

Download SKILL.mdSave it as .claude/skills/generate-changelog/SKILL.md (or your agent's skills folder).
name
generate-changelog
description
Generate a user-facing changelog entry for a new Android release from the unreleased changelog fragments, audited against git commits since the last shipped tag. Updates changelog.json and consumes the fragments.
user_invocable
true

Generate Changelog

Generate a changelog entry for a new release from the fragments in android/changelog.d/, maintained at commit time (rules in .claude/rules/changelog.md), audited against git commits since the last shipped tag.

This skill is invoked automatically by /deploy-android. It can also be run standalone.

Inputs

You need two values — either passed as arguments or calculated the same way /deploy-android does:

  • VERSION_NAME: date-based version, YYYY.MM.DD (e.g., 2026.09.23)
  • TAG: vYYMMDDNN (e.g., v26092301)

Steps

1. Collect the unreleased changes
bash
git fetch origin main --quiet

Run support/scripts/changelog-gather.sh, which merges the fragments (one <issue>-<slug>.json per change, plus SINCE) into one {since, features, improvements, fixes} document. This is the primary source: whoever made each change recorded it when committing it.

  • since (from android/changelog.d/SINCE) — the last tag that actually shipped to users. This is the release baseline, not git describe: a tag can exist on a build that was withdrawn before users saw it, and SINCE is the only record of what really shipped.
  • features / improvements / fixes — the draft entry lines, each with the commits that contributed.

The git log since since is an audit for anything missed, not the source. Run it with full commit messages and file stats so you can understand the actual changes rather than guessing from subject lines:

bash
git log <SINCE>..origin/main --no-merges --stat -- "android/"

If the audit turns up a user-facing change that is missing from the fragment, add it to the entry, and tell the user the fragment discipline slipped so it can be corrected going forward.

Anti-pattern — do NOT skim with subject lines only. --oneline strips the body, which is where user-facing impact actually lives. A perf(playback) commit might be a fail-fast change, not a speed-up; a fix(app) commit might be internal hardening for a bug no user ever saw. Read the body of every commit you're considering including or dismissing.

If SINCE is empty (bootstrap before the first tagged release under this scheme), fall back to recent commits:

bash
git log origin/main --no-merges --stat -20 -- "android/"

If the fragment and the audit are both empty, tell the user and stop.

Understanding ambiguous commits

When a commit subject is unclear about the user-facing impact, read the actual diff:

bash
git show <commit-hash> -- "android/"

Only do this for commits where the subject + body + file stats aren't enough to confidently describe the user impact.

The before-state hard rule

Any line implying a before-state ("no longer", "now", "instead of", "faster", "fixed") must be checked against the source code at the last shipped tag, never against commit messages or the previous changelog entry:

bash
git show <SINCE>:<path>
git diff <SINCE>..HEAD -- <path>

If the before-state never shipped — the feature was itself added since since and then polished — the line is not a fix: fold it into the feature's own description, or drop it.

When in doubt, ask

The user reviews each release. If you're unsure whether to include a particular item, ask before generating the JSON. A brief question is much cheaper than a wrong release note.

Show full SKILL.md (289 more words)Show less
A short changelog is better than a wrong one

If after filtering you only have one user-facing change, write a one-bullet changelog. Don't pad with marginal items under "improvements". Single-fix releases are normal — say so plainly.

2. Generate the changelog entry

Read the commits and write plain, friendly lines a user would understand — not developer jargon. Look at existing entries in app/src/main/assets/changelog.json for tone.

Style:

  • Plain language, no em dashes, no filler editorialising ("for a cleaner look", "for a better experience") — state the change.
  • No audience labels ("Alpha testers:").
  • One line per change, most exciting/impactful first within each category.
  • Omit empty categories from the entry (don't write "features": [] if there are none).
3. Output format

Match the existing schema in android/app/src/main/assets/changelog.json:

json
{
  "versionName": "2026.09.23",
  "releaseDate": "23/09/2026",
  "features": ["feature 1", "feature 2"],
  "fixes": ["fix 1"],
  "improvements": ["improvement 1"],
  "notes": []
}
  • versionName is the date-based YYYY.MM.DD form (matches TAG without the v and with dots).
  • releaseDate is DD/MM/YYYY, matching the format of every existing entry.
  • notes is an optional freeform blurb array (existing entries use it for a short aside from the developer) — leave it as [] unless the user supplies one; don't invent a "voice" for them.
4. Update changelog.json and consume the fragments

Read android/app/src/main/assets/changelog.json (a JSON array of release entries, newest first).

  • If an entry with the same versionName already exists, replace it.
  • Otherwise, prepend the new entry to the array.

Write the updated file. Ensure valid JSON with consistent formatting (2-space indent).

Then delete every consumed fragment and write the new baseline:

bash
git rm -q android/changelog.d/*.json
echo "<TAG>" > android/changelog.d/SINCE

Commit them together with the release: a changelog entry committed without its fragments removed makes the next release describe a delta against fragments that still claim the old baseline.

bash
git add -A android/app/src/main/assets/changelog.json android/changelog.d
git commit -m "docs(app): update changelog for $VERSION_NAME"

This repo has no Play Store listing or release-notes automation (no fastlane) — the in-app changelog is the only user-facing release note. Nothing further to write.

© timusus, Apache-2.0. 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/generate-changelog of timusus/Shuttle2.

Open the folder on GitHubat commit e05449e

Compare with similar skills

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

Generate Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Generate Changelog this skilltimusus/Shuttle2229—~1.5kAutomated safety check: PassApache-2.0
Commitmanhpham90vn/Deskhub133—~978Automated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Commitizencommitizen-tools/commitizen3.5k—~839Automated safety check: PassMIT

Similar skills

  • Commit

    manhpham90vn/Deskhub

    Write a Deskhub commit message. An agent skill from manhpham90vn/Deskhub.

    133 GitHub stars~978 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

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

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

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Commitizen

    commitizen-tools/commitizen

    A skill your agent uses for tasks involving Conventional Commits, commit message validation, Commitizen configuration, semantic version bumps, changelog generation, or CI/release automation with the…

    3.5k GitHub stars~839 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Commit And PR Messages

    superplanehq/superplane

    Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…

    7.7k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from timusus/Shuttle2

All 9 skills in this repo

  • Debug Receivers

    timusus/Shuttle2

    Drive the S2 debug build's playback and queue over ADB broadcasts — play the whole library, play/pause, skip, seek, remove a queue item, toggle shuffle/repeat, dump playback state as JSON, reimport…

    229 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Deploy Android

    timusus/Shuttle2

    Deploy the Android app to the Play Store via GitHub Actions.

    229 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Reply Reviews

    timusus/Shuttle2

    Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post.

    229 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Check

    timusus/Shuttle2

    Run lint + unit tests, investigate and fix failures. An agent skill from timusus/Shuttle2.

    229 GitHub stars~449 tokensUpdated today
    Auto-check passed

  • Deploy iOS

    timusus/Shuttle2

    Deploy Shuttle Music for iOS to TestFlight from this Mac. An agent skill from timusus/Shuttle2.

    229 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Emulator Check

    timusus/Shuttle2

    Verify an S2 change on the WSL desktop emulator in minutes — build once, lease a lane, install, run the scripted playback checks (debug receivers) and Maestro UI flows, add a new check, stop the lane.

    229 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Generate Changelog

What does Generate Changelog do?

Generate a user-facing changelog entry for a new Android release from the unreleased changelog fragments, audited against git commits since the last shipped tag. Generate Changelog is an agent skill from timusus/Shuttle2. Generate a user-facing changelog entry for a new Android release from the unreleased changelog fragments, audited against git commits since the last shipped tag.

When should I use Generate Changelog?

Generate Changelog fits situations like: tasks that involve Changelog and release notes; tasks that involve Commit messages.

How do I install Generate Changelog in Claude Code?

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

How do I install Generate Changelog in Codex?

Run `npx skills add timusus/Shuttle2 --skill generate-changelog -a codex`. Or copy the skill folder (.claude/skills/generate-changelog in timusus/Shuttle2) into .agents/skills/generate-changelog in your project. Codex loads it when a task matches its description.

Can I use Generate 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 timusus/Shuttle2 --skill generate-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/generate-changelog, .gemini/skills/generate-changelog, .github/skills/generate-changelog and .opencode/skills/generate-changelog in your project.

What does Generate Changelog need to run?

Going by SKILL.md and its folder, Generate Changelog needs the command-line tools its instructions call (git).

Does Generate Changelog access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

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

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

How many tokens does Generate Changelog use?

About 1.5k tokens (SKILL.md is roughly 6.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 Generate Changelog?

Skills that share tags, products or a category with Generate Changelog: Commit (manhpham90vn/Deskhub, 133 stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Generate Changelog?

timusus (a GitHub user) maintains it in timusus/Shuttle2, which has 229 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

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