An append-only skill for recording shipped software work in a monthly changelog. It keeps release history in dated files and links those files from an index.

Use it when work ships, when preparing release notes, or when someone asks what changed during the month.

It prevents shipped history from being silently rewritten and gives each session a concise record of recent changes.

changelog — Skill for Claude Code by MedAdemBHA: An append-only skill for recording shipped software work in…

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.

agentmods

npx agentmods add skills/medadembha/docflow/changelog

Any agent

npx skills add MedAdemBHA/docflow --skill changelog

Clone the repo

git clone --depth 1 https://github.com/MedAdemBHA/docflow

Made for: Claude Code.

Or install docflow, the plugin that ships this one along with the rest of its 9 skills, 3 commands.

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/medadembha/docflow/changelog.svg)](https://agentmods.dev/skills/medadembha/docflow/changelog)

Your own site

<a href="https://agentmods.dev/skills/medadembha/docflow/changelog"><img src="https://agentmods.dev/badge/skills/medadembha/docflow/changelog.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

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.00043	$0.00956
Opus 5	$0.00022	$0.00478
Sonnet 5	$0.00009	$0.00191
Haiku 4.5	$0.00004	$0.00096

Measured 6d ago against content hash 55553a874770, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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.

skills/changelog/SKILL.md · 96 lines

How it starts

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

changelog

The memory of the knowledge base. Every month gets one file; history is append-only. This is what the SessionStart hook surfaces so the agent starts each session knowing recent work. Pairs with author and router.

Golden rule: never delete or rewrite shipped history. Reversals get a new entry, not an edit.

Writing style (enforce)

Direct, tech + business. No filler. Outcome first.

Each entry = a small table (Outcome / Delivered / Business impact / Commits). No narrative paragraphs.
Summary = 4 bullets max: release type, biggest business change, biggest technical change, prod risk/action.
Concrete only: feature names, paths, hashes, numbers. Cut adjectives.

1 — One file per month

changelog/(mmm-yy).md — lowercase 3-letter month + 2-digit year: (apr-26).md, (may-26).md. changelog/README.md is the index: a table of | Month | Highlights |, newest first.

Link to a month file (parens need angle brackets): [may-26](<(may-26).md>).

2 — Anatomy of a month file

# Month YEAR — <release / period title>

> Window: `<base>` (`hash`, date) → `<head>` (`hash`, date). Scope: `N` commits.

## Summary
- Release type: patch | feature | architectural
- Biggest business change: <one line>
- Biggest technical change: <one line>
- Risk / action for prod: <one line>

## What Changed

### 1. <Feature / theme>
| | |
|---|---|
| Outcome | <one line> |
| Delivered | <bullet; bullet> |
| Business impact | <one line> |
| Commits | `<hash>` <desc>; `<hash>` <desc> |

### 2. <next theme>

A reader skimming the Outcome rows alone should understand the release.

3 — The shipping flow (where changelog fits)

The roadmap (plans/upcoming/) and the changelog are two ends of one pipe:

plans/upcoming/{critical,now,next,later}.md   ── ships ──►   changelog/(mmm-yy).md
        (what's coming)                                        (what landed)

When something ships:

Move the line out of the plans/upcoming/* horizon — don't let shipped work linger there (it kills the roadmap's signal).
Add / update the entry in the current changelog/(mmm-yy).md.
Cross-link: the feature plan's ## What shipped table references the changelog month; the ADR/spec stay linked from the plan.
If a known bug got fixed, move it from reviews/bugs/open.md to reviews/bugs/fixed.md with the commit ref.

Read the full file on GitHub · 96 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.

6d ago First seen · 96 lines · 43 tokens per session scan A 55553a874770

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository MedAdemBHA/docflow (41 stars, last pushed 22d ago), licensed MIT. It adds 43 tokens to every session and 956 once invoked, about $0.0002 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 Writing and docs ai-agents claude-code-plugin codex-plugin documentation

deploy-steward

Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.

SethGammon/Citadel · 56 tokens

han-release

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…

testdouble/han · 172 tokens

ship-item

Ship a plan/todo item in a documentation-led repo — run the verify gate, integrate per the repo's model (fast-forward or PR), git mv todo→done with a shipped footer, advance the owning ADR(s) to Implemented, regenerate INDEX. Use when the user says "ship this", "complete the plan item", "mark done", "close out the…

EvolveHQ/docflow · 87 tokens

changelog

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

changelog

Writing style (enforce)

1 — One file per month

2 — Anatomy of a month file

3 — The shipping flow (where changelog fits)

What this file has done since we first saw it

Other skills, from other repositories

deploy-steward

han-release

ship-item

release

release-support

release