Borrowing it
Nothing to install: this file belongs to Flexonze/claude-init. 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/Flexonze/claude-init/main/.claude/skills/update-changelog/SKILL.mdgit clone --depth 1 https://github.com/Flexonze/claude-initWrote 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/flexonze/claude-init/update-changelog)<a href="https://agentmods.dev/skills/flexonze/claude-init/update-changelog"><img src="https://agentmods.dev/badge/skills/flexonze/claude-init/update-changelog.svg" alt="Measured on agentmods" height="20"></a>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.00016 | $0.00305 |
| Opus 5 | $0.00008 | $0.00152 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
update-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 7d 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.
What it actually says
Update Changelog
Update the project's changelog based on the commits in the current branch.
Instructions
-
Identify the changelog file
- Look for
CHANGELOG.md,HISTORY.md, or similar - Note the existing format and style
- Look for
-
Analyze the current branch
- Get the branch name:
git branch --show-current - Get commits since branching from main:
git log main..HEAD --oneline - Read the full commit messages for context:
git log main..HEAD
- Get the branch name:
-
Categorize changes
- Group commits by type:
- Added (new features)
- Changed (modifications to existing features)
- Fixed (bug fixes)
- Removed (removed features)
- Security (security fixes)
- Deprecated (soon-to-be removed features)
- Group commits by type:
-
Update the changelog
- Add a new "Unreleased" section if needed
- Write clear, user-facing descriptions (not just commit messages)
- Follow the existing format and style of the changelog
- Link to relevant issues/PRs if the project does that
Examples
- "Update the changelog with my changes"
- "Add my branch changes to CHANGELOG.md"
- "What should I add to the changelog?"
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.
- 7d ago First seen · 42 lines · 16 tokens per session scan A 717206d857ae
update-changelog is a skill published in the GitHub repository Flexonze/claude-init (10 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 305 once invoked, about $0.0001 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-31.
Other skills, from other repositories
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…
version-control
Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.
semantic-versioning
Use when committing or pushing changes and the repository needs a version bump. Analyzes commits using conventional commit prefixes to determine whether the next release is a major, minor, or patch increment. Also use when the user asks about versioning, release planning, or changelog generation.
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.