Agent skill

Changelog

by ratel-ai in ratel-ai/ratel

Update per-package CHANGELOG.md files for a Ratel release. An agent skill from ratel-ai/ratel.

MITAuto-check passedDevelopment

Install Changelog

skills CLI
$ npx skills add ratel-ai/ratel --skill changelog -a claude-code

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

GitHub CLI
$ gh skill install ratel-ai/ratel 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/ratel-ai/ratel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/changelog .claude/skills/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
changelog
GitHub stars
471
Token cost
~1.6k tokens
SKILL.md length
690 words
Files
2
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Update per-package CHANGELOG.md files for a Ratel release. An agent skill from ratel-ai/ratel.

  • Works in 7 steps: Pick the unit and read its version → Determine the diff range → Generate the draft → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Release units it touches, Procedure, Conventions and Why this exists
  • Runs Shell scripts from its folder; calls node, git and bash

What it does

Changelog is an agent skill from ratel-ai/ratel. Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc. sections into a single X.Y.Z section). Invoke before tagging a release.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `draft.sh`).

It sits in Development, covering Changelog and release notes. It works with Model Context Protocol, Git, Vercel AI SDK and npm. The repository describes itself as: Context engineering for AI agents. ~80% fewer tokens. Fix tool overload. Skills and memory with in-process BM25 and semantic retrieval. Progressive Disclosure. No vector DB. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/changelog”

Requirements

  • A Bash shell

Workflow steps

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

  1. Pick the unit and read its version
  2. Determine the diff range
  3. Generate the draft
  4. Branch on RC vs GA
  5. Curate with the user
  6. Write the file
  7. Remind

What it can do on your machine

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

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • git
    • bash

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

  • Network

    Links to these hosts (documentation or services it may open):

    • 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

Changelog loads about 1.6k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 690 words of instructions outside code blocks.

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

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 ratel-ai/ratel at commit 4e534ac, republished under its MIT licence (© ratel-ai). 690 words, ~1,550 tokens.

Download SKILL.mdSave it as .claude/skills/changelog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
changelog
description
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc.* sections into a single X.Y.Z section). Invoke before tagging a release.

/changelog

Updates a release unit's CHANGELOG.md in preparation for tagging it. Ratel releases per unit (ADR-0008): each unit ships on its own tag (<prefix>-v*) at its own version. For workflow-wired units, .github/workflows/release.yml rejects a tag whose unit CHANGELOG doesn't contain the version being released. vercel-ai-sdk is temporarily published manually via scripts/publish-rc.sh; still run this skill before its tag even though the workflow gate does not cover it yet.

Run it once per unit you're releasing.

Release units it touches

The units and their manifests/CHANGELOGs live in one registry — scripts/release-units.mjs — which every release tool reads. Run node scripts/release-units.mjs --list for the authoritative set; the current eight units are:

UnitRegistryCHANGELOG path
coreratel-ai-core (crates.io)src/core/CHANGELOG.md
sdk-ts@ratel-ai/sdk (npm)src/sdk/ts/CHANGELOG.md
sdk-pyratel-ai (PyPI)src/sdk/python/CHANGELOG.md
telemetry-coreratel-ai-telemetry (crates.io)src/telemetry/core/CHANGELOG.md
telemetry-ts@ratel-ai/telemetry (npm)src/telemetry/ts/CHANGELOG.md
telemetry-pyratel-ai-telemetry (PyPI)src/telemetry/python/CHANGELOG.md
vercel-ai-sdk@ratel-ai/vercel-ai-sdk (npm)src/adapters/ts-vercel-ai-sdk/CHANGELOG.md
mastra@ratel-ai/mastra (npm)src/adapters/ts-mastra/CHANGELOG.md

@ratel-ai/mcp-server lives in ratel-ai/ratel-mcp and maintains its own CHANGELOG there.

Procedure

1. Pick the unit and read its version

If the user hasn't named the unit, run node scripts/releasable.mjs — it lists which units have commits since their last release tag. Pick the unit $UNIT being released.

Read its canonical version:

bash
node scripts/release-units.mjs --version "$UNIT"   # -> $TARGET

If the user supplies a different version explicitly, prefer that and warn them the working tree disagrees.

2. Determine the diff range

The range is from the unit's own last release tag to HEAD:

bash
prefix=$(node scripts/release-units.mjs --tag-prefix "$UNIT")
FROM=$(git describe --tags --match "${prefix}*" --abbrev=0 2>/dev/null || true)

If $FROM is empty the unit has never shipped; the whole history is in range.

3. Generate the draft
bash
bash .claude/skills/changelog/draft.sh --unit "$UNIT"

It emits a single ### <package-name> block for the unit, containing either Keep-a-Changelog sections (### Added, ### Fixed, ### Changed) or the sentinel _No user-facing changes._. (Omit --unit to draft every unit at once.) With no <from-ref> argument the script ranges each unit from its own last tag automatically.

If draft.sh exits 127, git-cliff is missing. Tell the user how to install it (the script's stderr already does), and stop.

4. Branch on RC vs GA

Inspect $TARGET, and edit only this unit's CHANGELOG:

  • RC (X.Y.Z-rc.N): prepend a new section above the most recent versioned section:

    ## [X.Y.Z-rc.N] - YYYY-MM-DD
    
    <draft content for the unit, or the sentinel>

    Use today's date in YYYY-MM-DD (UTC).

  • GA (no -rc suffix): enter GA-collapse mode:

    1. Find every ## [X.Y.Z-rc.*] section already present that matches the same MAJOR.MINOR.PATCH as $TARGET.
    2. Union their bullet entries (per subsection: ### Added, ### Changed, ### Fixed) with the new draft entries from step 3 (commits since the last RC tag).
    3. Deduplicate bullets within each subsection (case-insensitive, whitespace-normalised).
    4. Drop the _No user-facing changes._ sentinel if any real entries exist; keep it only if the unioned set is empty.
    5. Replace all the matched RC sections with a single ## [X.Y.Z] - YYYY-MM-DD section containing the merged content.
    6. Leave non-matching prior versions (e.g. ## [0.1.4]) untouched.
Show full SKILL.md (247 more words)Show less
5. Curate with the user

Show the unit's CHANGELOG pending changes in the conversation. Ask the user to confirm or edit. Common curation moves:

  • Rephrase bullets for user-facing clarity (the draft uses commit subjects verbatim).
  • Drop bullets that are not user-visible (internal refactors that slipped past cliff.toml's skip rules).
  • Merge duplicates that survived deduplication.
  • Promote / demote between Added / Changed / Fixed if the commit prefix was wrong.
6. Write the file

Once approved, write only this unit's CHANGELOG using the Edit tool. Do not commit. The release commit is the user's responsibility — they typically include the CHANGELOG alongside the version bump in a single release: <unit>-vX.Y.Z commit.

If releasing more than one unit, repeat from step 1 for each.

7. Remind

Tell the user:

  • The CHANGELOG is staged in the working tree (unstaged).
  • Next step is the release commit + <unit>-v<version> tag + push.
  • For workflow-wired units, the release.yml tag-version-check job verifies the unit's CHANGELOG contains the tag version; if it doesn't, the release is blocked.
  • For vercel-ai-sdk, publish manually with scripts/publish-rc.sh after the tag push; its CHANGELOG is not workflow-gated yet.

Conventions

  • Date format: YYYY-MM-DD in UTC.
  • Subsection order: ### Added, ### Changed, ### Fixed, ### Removed, ### Deprecated, ### Security. Omit empty subsections.
  • Sentinel: _No user-facing changes._ for a unit with no in-scope commits.
  • Keep ## [Unreleased] at the top — it stays empty between releases.

Why this exists

ADR 0008 (docs/adr/0008-release-engineering.md) records the per-unit tag/version split, the CHANGELOG mechanism, and the rationale. Read it if you're unsure why something is structured the way it is.

© ratel-ai, MIT. 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 .claude/skills/changelog of ratel-ai/ratel.

  • SKILL.md
  • draft.sh

Open the folder on GitHubat commit 4e534ac

Compare with similar skills

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.

Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Changelog this skillratel-ai/ratel471—~1.6kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Hunk Release Workflowmodem-dev/hunk9.6k—~3.8kAutomated safety check: PassMIT
AionUi Version BumpiOfficeAI/AionUi33k—~2.1kAutomated safety check: PassApache-2.0
Figma Typings Auditawdr74100/figwright1k—~3.3kAutomated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT

Similar skills

  • 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 2 days ago
    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.6k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • AionUi Version Bump

    iOfficeAI/AionUi

    Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.

    33k GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Figma Typings Audit

    awdr74100/figwright

    Upgrade @figma/plugin-typings and absorb what the new version exposes.

    1k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Git Changes Reporter

    No-Trade-No-Life/Yuan

    生成结构化 git 变更报告(JSON + Markdown)。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要",或需要分析指定 commit 区间的代码变更。包含三元组结构(设计意图、核心代码、影响范围)的语义化报告,适用于代码审查、发布说明、团队同步、CI/CD 等场景。

    352 GitHub stars~1.2k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

More from ratel-ai/ratel

  • Publish local .claude skills/loops to Ametyst — verbatim, flattened, no brain rewrite; optional retire-local (MOVE originals to deprecated-skills/, never delete) makes Ametyst the source of truth.

    471 GitHub stars~197 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Changelog

What does Changelog do?

Update per-package CHANGELOG.md files for a Ratel release. An agent skill from ratel-ai/ratel. Changelog is an agent skill from ratel-ai/ratel.md files for a Ratel release.

When should I use Changelog?

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

How do I install Changelog in Claude Code?

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

How do I install Changelog in Codex?

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

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

What does Changelog need to run?

Going by SKILL.md and its folder, Changelog needs a shell for the scripts in its folder and the command-line tools its instructions call (node, git and bash). Our summary lists: A Bash shell.

Does Changelog access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

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

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

About 1.6k 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 Changelog?

Skills that share tags, products or a category with Changelog: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Hunk Release Workflow (modem-dev/hunk, 9.6k stars), AionUi Version Bump (iOfficeAI/AionUi, 33k stars) and Figma Typings Audit (awdr74100/figwright, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changelog?

ratel-ai (a GitHub organization) maintains it in ratel-ai/ratel, which has 471 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.

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