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

Changelog CLI

by heygen-com in heygen-com/heygen-cli

Generate a user-facing changelog for the next stable release.

Apache-2.0Auto-check passedDevelopment

Install Changelog CLI

skills CLI
$ npx skills add heygen-com/heygen-cli --skill changelog-cli -a claude-code

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

GitHub CLI
$ gh skill install heygen-com/heygen-cli changelog-cli --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/heygen-com/heygen-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/changelog-cli .claude/skills/changelog-cli && 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
changelog-cli
GitHub stars
145
Token cost
~997 tokens
SKILL.md length
421 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate a user-facing changelog for the next stable release.

  • Works in 5 steps: Determine the range → Read the full commit details → Categorize and write the changelog → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Step 1: Determine the range, Step 2: Read the full commit…, Step 3: Categorize and write… and Step 4: Format the output, plus 1 more section
  • Calls git and gh

What it does

Changelog CLI is an agent skill from heygen-com/heygen-cli. Generate a user-facing changelog for the next stable release. Reads git log between the last stable tag and HEAD, categorizes changes, and outputs formatted release notes. Use before triggering a stable release.

Its SKILL.md is about 1000 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 HeyGen, Git and Go. The repository describes itself as: Create AI videos from the terminal. Official CLI for the HeyGen video generation API. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/changelog-cli”

Workflow steps

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

  1. Determine the range
  2. Read the full commit details
  3. Categorize and write the changelog
  4. Format the output
  5. Present for review

What it can do on your machine

Read from SKILL.md and the folder at commit 7ef65c2. 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
    • gh

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

  • Network

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

Changelog CLI loads about 997 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 421 words of instructions outside code blocks.

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

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 heygen-com/heygen-cli at commit 7ef65c2, republished under its Apache-2.0 licence (© heygen-com). 421 words, ~997 tokens.

Download SKILL.mdSave it as .claude/skills/changelog-cli/SKILL.md (or your agent's skills folder).
name
changelog-cli
description
Generate a user-facing changelog for the next stable release. Reads git log between the last stable tag and HEAD, categorizes changes, and outputs formatted release notes. Use before triggering a stable release.
argument-hint
[version, e.g. v0.0.6]

Changelog Generator

Generate release notes for a stable release by summarizing git commits since the last stable tag.

Step 1: Determine the range

bash
# Find the last stable tag
LAST_STABLE=$(git tag --list 'v*' --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1)

If LAST_STABLE is empty (first stable release), use the full history by omitting the range:

bash
# If LAST_STABLE is set:
git log "${LAST_STABLE}..origin/main" --oneline

# If LAST_STABLE is empty (first release):
git log origin/main --oneline

If a version argument was provided (e.g., /changelog-cli v0.0.6), use it as the heading. Otherwise, infer the next version by bumping the patch of $LAST_STABLE (or use v0.1.0 if no stable tag exists).

Step 2: Read the full commit details

Use the same range logic from Step 1 (with or without $LAST_STABLE):

bash
# With a previous stable tag:
git log "${LAST_STABLE}..origin/main" --format="### %h%n%s%n%n%b%n---"

# First release (no stable tag):
git log origin/main --format="### %h%n%s%n%n%b%n---"

Also read the PR descriptions for any merged PRs in the range to get richer context on what changed and why:

bash
# Extract PR numbers from commit messages (works on both GNU and BSD grep)
git log ${LAST_STABLE:+"${LAST_STABLE}.."}origin/main --oneline | grep -o '#[0-9]\+' | tr -d '#' | sort -u

For each PR number, read the PR body:

bash
gh pr view <number> --json title,body --jq '.title + "\n" + .body'

Step 3: Categorize and write the changelog

Group changes into these categories (omit empty categories):

  • New - new commands, features, or capabilities
  • Improved - enhancements to existing behavior
  • Fixed - bug fixes
  • Internal - changes with no user-visible effect (CI, refactors, docs)

A codegen resync is not automatically Internal. What it did to the command surface is what a user cares about, so a resync that added a command or a flag is a New entry naming that command or flag, carrying the resync's PR number. List a resync under Internal only when it changed nothing a user can type.

The commit subject does not tell you which case you are in -- every resync reads codegen: resync gen/ from EF <sha>. Get the surface change from the resync PR's body, which lists new and changed commands, or from scripts/release-surface.sh diff <last-stable> origin/main.

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

Step 4: Format the output

Output the changelog in this format:

markdown
## <version> (<date>)

### New
- **Short title.** One-sentence description of what changed and why it matters. (#PR)

### Improved
- **Short title.** One-sentence description. (#PR)

### Fixed
- **Short title.** One-sentence description. (#PR)

### Internal
- Updated CI workflow (#PR)

Rules:

  • Write for CLI users, not contributors. Focus on what changed from the user's perspective, not implementation details.
  • Each entry should be one sentence. Lead with what the user can now do or what was fixed, not what code changed.
  • Include the PR number in parentheses at the end of each entry.
  • Do not fabricate changes. Only include what is in the git log.
  • Collapse CI changes and doc updates into the Internal section with minimal detail.
  • Never let an Internal entry restate something already listed above it. If a resync's only content is the command it added, that command's New entry is the whole story and a second Internal line for the same PR adds nothing.

Step 5: Present for review

Print the formatted changelog and ask the releaser to confirm or edit before proceeding. Once confirmed, the releaser should paste it into the GitHub release notes when the release is published.

© heygen-com, 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/changelog-cli of heygen-com/heygen-cli.

Open the folder on GitHubat commit 7ef65c2

Compare with similar skills

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

Changelog CLI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changelog CLI this skillheygen-com/heygen-cli145—~997Automated safety check: PassApache-2.0
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause
Releasejrswab/axe895—~1.4kAutomated safety check: PassApache-2.0
Releaseggwhite/go-masker130—~938Automated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT

Similar skills

  • 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

  • Release

    jrswab/axe

    Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.

    895 GitHub stars~1.4k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Release

    ggwhite/go-masker

    Release a new version of go-masker: update CHANGELOG.md from git log, create GitHub release.

    130 GitHub stars~938 tokensUpdated 3 mo ago
    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

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

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

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

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

More from heygen-com/heygen-cli

  • E2E CLI Test

    heygen-com/heygen-cli

    End-to-end test of the heygen CLI against the live API. An agent skill from heygen-com/heygen-cli.

    145 GitHub stars~2.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Changelog CLI

What does Changelog CLI do?

Generate a user-facing changelog for the next stable release. Changelog CLI is an agent skill from heygen-com/heygen-cli. Generate a user-facing changelog for the next stable release.

When should I use Changelog CLI?

Changelog CLI fits situations like: tasks that involve Changelog and release notes.

How do I install Changelog CLI in Claude Code?

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

How do I install Changelog CLI in Codex?

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

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

What does Changelog CLI need to run?

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

Does Changelog CLI access the network?

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

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

Changelog CLI 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 Changelog CLI use?

About 997 tokens (SKILL.md is roughly 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 Changelog CLI?

Skills that share tags, products or a category with Changelog CLI: Go-Redis Release Preparation (redis/go-redis, 22k stars), Release (jrswab/axe, 895 stars), Release (ggwhite/go-masker, 130 stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changelog CLI?

heygen-com (a GitHub organization) maintains it in heygen-com/heygen-cli, which has 145 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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