Borrowing it
Nothing to install: this file belongs to Sma1lboy/rove. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Sma1lboy/rove/main/.claude/skills/changelog-generator/SKILL.mdgit clone --depth 1 https://github.com/Sma1lboy/roveWrote 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.
[](https://agentmods.dev/skills/sma1lboy/rove/changelog-generator)<a href="https://agentmods.dev/skills/sma1lboy/rove/changelog-generator"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/changelog-generator/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.
<a href="https://agentmods.dev/skills/sma1lboy/rove/changelog-generator"><img src="https://agentmods.dev/badge/skills/sma1lboy/rove/changelog-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00101 | $0.01597 |
| Opus 5 | $0.00051 | $0.00798 |
| Sonnet 5 | $0.00020 | $0.00319 |
| Haiku 4.5 | $0.00010 | $0.00160 |
Grade A, and why
changelog-generator 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Generator (Rove)
Drafts release notes as Changesets — one .changeset/<name>.md file per change — in Rove's house style. scripts/release.sh (via changeset version) later consumes them into packages/kobe/CHANGELOG.md and the GitHub release body. See docs/RELEASING.md for the full flow.
When to use
- The user says "draft changelog", "write release notes", "add a changeset", "what changed since v0.X.Y", or similar.
- After landing a user-facing change that has no changeset yet (e.g. it was committed before this skill existed, or in a batch that skipped them).
- Before cutting a release tag — to backfill changesets for anything user-facing that slipped through, so the generated notes are complete.
Rove project conventions (load-bearing)
Every rule in this section overrides the generic guidance further down.
File format — a changeset, not a CHANGELOG edit
-
Do not hand-edit
packages/kobe/CHANGELOG.mdor invent a## [Unreleased]section — that file is generated. -
Each change is a new file
.changeset/<two-words-random>.md(thechangesetCLI names it; if writing by hand, any unique kebab name works). Shape:--- "@sma1lboy/rove": patch --- Single-line user-facing summary. This text lands verbatim under the next release and in the GitHub release body. -
The canonical frontmatter bump key is
@sma1lboy/rove, with valuepatch|minor|major. -
Default to
patchfor every change, including features and pre-1.0 breaking changes. Useminorormajoronly when the user explicitly requests that bump in the current turn. -
The bump type is the category — Changesets groups output under
### Minor Changes/### Patch Changesautomatically. Don't write### Added/### Fixedheadings yourself. -
One changeset per coherent change. A batch that did three user-visible things → three changesets (or one with three bullets if they're one feature). Prefer the
changesetCLI:bun run changeset(interactive) writes the file for you.
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.
- 11d ago First seen · 95 lines · 101 tokens per session scan A 277472207011
changelog-generator is a skill published in the GitHub repository Sma1lboy/rove (122 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,597 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.
Other skills, from other repositories
fable-release
Audit and certify repository merge and release readiness against required quality gates, clean git working trees, and verified distribution artifacts. Use when preparing a release tag, validating release checklist criteria, publishing npm/PyPI packages, or certifying a branch for merge — even if the user does not…
pr-explainer
Use when writing pull request descriptions, release notes, or summary diffs.
dev-git-workflow
Designs team Git workflows for branching, PRs, and releases. Use when choosing branching models, stacked PRs, merge queues, worktree isolation for agents, or collaboration rules.
deploy-safely
Build, test, push, deploy, and verify with rollback through Git on failure.
npm-publish
Use when publishing this package to npm — a version release (npm publish), verifying the registry/pi.dev listing, or diagnosing npm auth failures (E403 2FA/token errors). Token-based flow via NPMTOKEN in .env.local with a temp userconfig, the leakage gate before every publish, post-publish verification and…
ship-task
Use to wrap up a finished task - set status to done, merge, clean up.