Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. 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/dixus/claudeframework/main/.claude/skills/changelog/SKILL.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/changelog)<a href="https://agentmods.dev/skills/dixus/claudeframework/changelog"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/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.
<a href="https://agentmods.dev/skills/dixus/claudeframework/changelog"><img src="https://agentmods.dev/badge/skills/dixus/claudeframework/changelog.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.01965 |
| Opus 5.5 | $0.00025 | $0.00786 |
| Sonnet 5.5 | $0.00013 | $0.00393 |
| Haiku 4.5 | $0.00006 | $0.00197 |
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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write the per-ticket changelog for the current branch: changelog/<working-branch>.md.
One file per branch — not a shared CHANGELOG.md — so changelog updates never conflict on the main branch.
Why this skill exists
/ship writes the changelog as Step 5b. When you work without /ship, it never gets written, and three things fail silently:
- The work item's "manual steps required" flag (if the project's tracker has one) is derived from the
## Manual Stepssection. No changelog → the flag stays unset even when the ticket needs a DB script, a routing change or a cache flush. - The tracker comment that mirrors those steps into the work item is never posted. Deployers then find them neither in the repo nor in the ticket.
/release-notesaggregates every changelog's## Manual Stepsintoreleases/<quarter>.md. A missing changelog means a missing entry — the person deploying never learns the step exists.
In all three cases a missing changelog is indistinguishable from "this ticket needs no manual steps". Nothing turns red. It surfaces when a deployment fails.
Step 1 — Determine the target file
Normal case: changelog/<working-branch>.md, using the full branch name.
changelog/1234.Improvement.Api.ChatSecureDefaults.md
PRD-mode: if $ARGUMENTS names a spec, or the branch is an epic branch hosting several PRDs, write changelog/<spec-name>.md instead (e.g. changelog/prd07-document-upload.md). An epic branch carries many PRDs as separate commits over weeks; a per-branch filename would overwrite each prior PRD's changelog. The spec name is unique per PRD and already used as the spec filename.
Idempotent: if the file exists, overwrite it with the current state. Never append, never create a second file.
Step 2 — Resolve ticket context from the branch
git rev-parse --abbrev-ref HEAD
Parse with the convention from .claude/rules/branch-management.md if the project defines one. The framework default:
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.
- 1mo ago First seen · 139 lines · 63 tokens per session scan A 025f8d25f0c5
changelog is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,965 once invoked, about $0.0003 per session on Opus 5.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-09-16.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…