Changelog Audit Agent Skill

Audit Warp CHANGELOG.md before a release: recover lost entries, sort by user impact, refine entry language, line-wrap, and (release-branch…

Context cost
17.1k tokensestimated from the bundle, loaded when it triggers
Bundle
3 files · 68.4 kBtext throughout, nothing executable
Licence
Apache-2.0the author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Audit Warp CHANGELOG.md before a release: recover lost entries, sort by user impact, refine entry language, line-wrap, and (release-branch mode) bump compare refs.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

changelogdocumentation

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md46.9 kB · preview
--- # SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. # SPDX-License-Identifier: Apache-2.0 name: changelog-audit license: Apache-2.0 ---
9# Changelog Audit
10
11Audits CHANGELOG.md before a Warp release. Operates in two modes auto-detected from the resolved ref name:
12
13- **Release-branch mode** (ref name matches ^release-): the upcoming release section is being finalized. Run all cleanup passes, promote [Unreleased] → [X.Y.Z], and bump the compare-link reference block at the bottom.
14- **Main mode** (anything else, including bare main): tidy the live [Unreleased] section in place. If main's CHANGELOG is out of sync with one or more released tags, also back-port the tag's section, dedupe redundant [Unreleased] entries, and rotate the compare-link refs. No rename of [Unreleased].
15
16Cleanup passes (some mode-conditional, run in this order):
17
18- **Phase 1.5 (main only, conditional) — Post-release sync.** When a stable tag exists whose [X.Y.Z] section is missing from main's CHANGELOG, back-port the section from the tag, dedupe [Unreleased] entries that already shipped, and rotate compare-link refs. Runs unconditionally when triggered (not skippable).
19- **Phase 2 — Lost-entry recovery.** Find entries that landed inside an already-released section due to merge=union and propose moves up.
20- **Phase 3 — Verify, consolidate, link metadata, and check section placement.** Confirm non-trivial entries are accurate against the actual code (run code if needed); merge "Add X / Fix X / Change X" sequences for never-shipped features into a single accurate entry; retro-search GitHub for missing GH refs; and re-classify entries that landed in the wrong subsection (e.g., a behavior change wrongly under Fixed) or are missing a **Breaking:** marker.
21- **Phase 4 — Impact sort.** Within each subsection, most user-impactful first; soft preference for keeping similar entries adjacent.
22- **Phase 5 — Language pass.** Drop entries with no user-facing impact, rewrite jargon-heavy entries, fan out to user-perspective subagents on ambiguous cases, then run the editorial conventions sweep (imperative mood, hyphenation, GH-link position, symbol formatting consistency).
23- **Phase 6 — Line-wrap and consolidated diff.** 120-char hard limit, prefer fewer lines, preserve semantic line breaks where they help raw-text readers.
24- **Phase 7 (release-branch only) — Promote + ref bump.** Rename header and update the link-reference block.
25
26Edits land in CHANGELOG.md directly. **All passes stage their changes to an in-memory buffer**; nothing is written until Phase 6 surfaces the consolidated diff and the user confirms. Phase 1.5 (post-release sync, on dedupe decisions), Pass 2 (lost-entry recovery), Pass 3 (consolidations and retro-GH ref insertions), and Pass 5 (rewrites and deletions) prompt before staging certain decisions so the user can decide on a per-candidate basis. Phase 7 (release-branch only) confirms its rename + ref-bump diff separately and writes after that confirmation.
27
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md6,937 words
Files3
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈90
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
17,010
on trigger
The instruction body and 2 supporting files, read only when the skill fires.
8.6%
of a 200k window
Ten skills this size would take about 86% of the window before you open a file.
050k100k150k200k context window

17.1k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

3 files, 68.4 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md46.9 kB
  • references/language-conventions.md17.0 kB
  • references/sorting-rubric.md4.5 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 3 files you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Changelog Audit · 17.1k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/changelog-audit/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/changelog-audit" ] && { [ ! -e .claude/skills/changelog-audit ] || { mv .claude/skills/changelog-audit "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/changelog-audit" .claude/skills/ && echo "Installed .claude/skills/changelog-audit"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add nvidia/changelog-audit

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/changelog-audit/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/changelog-audit/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/changelog-audit" ] && { [ ! -e ~/.claude/skills/changelog-audit ] || { mv ~/.claude/skills/changelog-audit "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/changelog-audit" ~/.claude/skills/ && echo "Installed ~/.claude/skills/changelog-audit" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/changelog-audit/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencenvidia/changelog-audit

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers2
Claim this skill