A release-notes helper that rebuilds the “Unreleased” section of each affected CHANGELOG.md, a file that records software changes. It uses commits and local changes, including in monorepos (repositories containing multiple packages), and follows the Keep a Changelog format.

Use it to prepare unreleased notes before publishing a new version, across one-package repositories or monorepos.

It removes the manual work of collecting recent changes and sorting them into release-note categories. It also identifies cases where the repository is not suitable for the task, such as having no changelog files.

changelog — Skill for Claude Code by juicesharp

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 juicesharp/rpiv-mono --skill changelog

Clone the repo

git clone --depth 1 https://github.com/juicesharp/rpiv-mono

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/changelog/github.svg)](https://agentmods.dev/skills/juicesharp/rpiv-mono/changelog)

Your own site

<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/changelog"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/changelog"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,463 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00098	$0.02463
Opus 5	$0.00049	$0.01231
Sonnet 5	$0.00020	$0.00493
Haiku 4.5	$0.00010	$0.00246

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

Security

Grade A, and why

changelog scanned grade A with 0 findings 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 12d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/rpiv-pi/skills/changelog/SKILL.md · 185 lines

How it starts

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

Generate CHANGELOG entries

You are tasked with regenerating the ## [Unreleased] section of every affected CHANGELOG.md in the repository so it reflects all change since the last release tag — committed and uncommitted alike.

Input

$ARGUMENTS — optional --since <ref> flag. Empty/literal → range starts at last_tag: from the Metadata block.

Metadata

node "${SKILL_DIR}/../_shared/changelog-bootstrap.mjs"

in_repo: — yes or no. Used by Step 1.1.
last_tag: — last release tag, or (no tags). Used by Step 1.3 and Step 2.1 when no --since is supplied.
---changelogs--- block — paths of every tracked CHANGELOG.md (one per line, empty if none). Used by Step 1.2.

Workflow

Bail-out checks
Determine the change range
Determine each CHANGELOG's scope and collect commits + uncommitted hunks
Classify and draft entries
Preview and confirm
Apply

Step 1: Bail-out checks

If in_repo: is no, tell the user "This directory is not a git repository." and stop.
If the ---changelogs--- block is empty, tell the user "No CHANGELOG.md found in the repository — create one (root or per-package) before running this skill." and stop.
If last_tag: is (no tags) AND $ARGUMENTS lacks --since <ref>, ask the user to supply --since <ref> and stop until they do.

Step 2: Determine the change range

Parse the input for a --since <ref> flag. If absent, use last_tag: from the Metadata block as SINCE.
The range is $SINCE..HEAD for committed changes, plus the current uncommitted+staged working tree.

Step 3: Determine each CHANGELOG's scope, then collect commits + uncommitted hunks

Each CHANGELOG.md discovered in Step 1.2 owns a path scope:

Nested CHANGELOG (e.g. packages/foo/CHANGELOG.md, apps/web/CHANGELOG.md): scope is its parent directory — packages/foo/, apps/web/.
Root CHANGELOG (CHANGELOG.md at repo root):
- If no nested CHANGELOGs exist: scope is the entire repository.
- If nested CHANGELOGs also exist: scope is the repository excluding every directory that owns a nested CHANGELOG. The root file captures repo-wide change (CI, build config, root README) that no per-package file would claim.

Read the full file on GitHub · 185 lines

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.

12d ago First seen · 185 lines · 98 tokens per session scan A f67f1554fe51

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository juicesharp/rpiv-mono (779 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 2,463 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

pack-submit

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.

aeonfun/aeon · 27 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens