update-changelog

update-changelog is a skill for Claude Code from noahlz/claude-plugins. It costs 26 tokens per session (1,312 once invoked), scanned B, original, MIT.

A changelog updater that reviews Git commits since the latest release and writes entries in the project's existing format. A changelog is a file that records notable changes between software releases.

In plain words
What is it for?
Use it to prepare changelog entries for new features, fixes, and other changes since the last release.
Why use it?
It removes the need to manually inspect commits and keep release notes consistent with the project.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Part of the dev-workflow plugin — 10 skills, 4 agents shipped together

Good fit Use it to prepare changelog entries for new features, fixes, and other changes since the last release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/noahlz/claude-plugins/update-changelog
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add noahlz/claude-plugins --skill update-changelog
Clone the repo
git clone --depth 1 https://github.com/noahlz/claude-plugins

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 10 skills, 4 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for update-changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/noahlz/claude-plugins/update-changelog/github.svg)](https://agentmods.dev/skills/noahlz/claude-plugins/update-changelog)
Your own site
<a href="https://agentmods.dev/skills/noahlz/claude-plugins/update-changelog"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/update-changelog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for update-changelog

Your own site · 80×15
<a href="https://agentmods.dev/skills/noahlz/claude-plugins/update-changelog"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/update-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01312
Opus 5 $0.00013 $0.00656
Sonnet 5 $0.00005 $0.00262
Haiku 4.5 $0.00003 $0.00131

Measured 9d ago against content hash 37fc4c3825c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

update-changelog scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- **Found** → `cat .claude/settings.plugins.update-changelog.json`, extract `changelogPath` as `CHANGELOG_PATH`. Verify with `git ls-files --error-unmatch "{{CHANGELOG_PATH}}" 2>/dev/null || test -f "{{CHANGELOG_PATH}}"`
plugins/dev-workflow/skills/update-changelog/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Write changelog entries for commits since the last release, matching the project's existing format.

Activate only on /update-changelog or explicit request. Follow steps EXACTLY.

Workflow Checklist

- [ ] 0. Config check
- [ ] 1. Detect latest tag
- [ ] 2. Collect commits
- [ ] 3. Read existing changelog
- [ ] 4. Filter and categorize (silent)
- [ ] 5. Present and confirm
- [ ] 6. Write changelog

SKILL_BASE_DIR: ${CLAUDE_SKILL_DIR}

⛔ If SKILL_BASE_DIR shows literal ${CLAUDE_SKILL_DIR}, halt: "This skill requires Claude Code 2.1.69 or higher."

Silence: Narrate only STEP_DESCRIPTION steps; execute all others silently. Format fidelity: Detect and match the existing changelog's format. Never impose a new one.


Step 0 — Config Check

Run: node "${CLAUDE_SKILL_DIR}/../../lib/check-skill-config.js" "./.claude/settings.plugins.update-changelog.json"

  • Foundcat .claude/settings.plugins.update-changelog.json, extract changelogPath as CHANGELOG_PATH. Verify with git ls-files --error-unmatch "{{CHANGELOG_PATH}}" 2>/dev/null || test -f "{{CHANGELOG_PATH}}". If missing, ask for correct path (default: ./CHANGELOG.md) and update config.
  • NOT_CONFIGURED → say config is missing. Ask: "Where is your changelog file? (default: ./CHANGELOG.md)" Store as CHANGELOG_PATH. Write: echo '{"changelogPath":"{{CHANGELOG_PATH}}"}' > .claude/settings.plugins.update-changelog.json

Step 1 — Detect Latest Tag

STEP_DESCRIPTION: "Detecting latest release tag"

Run: git tag --list --sort=-v:refname

Find the most recent semver-like tag (v1.2.3, 1.2.3, release-1.2.3, or any digits-and-dots pattern). Store as LATEST_TAG; strip prefix for LATEST_VERSION.

No semver tag → say so and HALT.

Step 2 — Collect Commits

STEP_DESCRIPTION: "Collecting commits since last release"

Run: git log {{LATEST_TAG}}..HEAD --pretty=format:"%h|%s|%b---END---"

Empty output → say "No changes since {{LATEST_TAG}}." and HALT.

Read the full file on GitHub · 133 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 133 lines · 26 tokens per session scan B 37fc4c3825c8

Subscribe to this mod's changes

update-changelog is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 1,312 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.