A changelog workflow based on Keep a Changelog, a common format for recording software changes under headings such as Added, Changed, Fixed, and Removed.

Use it after completing work, before releasing or tagging a version, or when creating or updating CHANGELOG.md.

It provides a consistent way to collect shipped work and prepare release notes before tagging or publishing a version.

changelog — Skill for Claude Code by tuliosousapro

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.

Any agent

npx skills add tuliosousapro/SaaS-blueprint --skill changelog

Clone the repo

git clone --depth 1 https://github.com/tuliosousapro/SaaS-blueprint

Made for: Claude Code.

Or install SaaS-blueprint, the plugin that ships this one along with the rest of its 14 skills.

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/tuliosousapro/saas-blueprint/changelog/github.svg)](https://agentmods.dev/skills/tuliosousapro/saas-blueprint/changelog)

Your own site

<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/changelog"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tuliosousapro/saas-blueprint/changelog"><img src="https://agentmods.dev/badge/skills/tuliosousapro/saas-blueprint/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00039	$0.00640
Opus 5	$0.00019	$0.00320
Sonnet 5	$0.00008	$0.00128
Haiku 4.5	$0.00004	$0.00064

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

skills/changelog/SKILL.md · 94 lines

How it starts

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

Changelog Skill

When to Use

After completing a sprint or shipping a feature.
Before tagging a release or pushing to main.
When the user asks "what changed?" or "update the changelog".

Reference

Keep a Changelog v1.1.0

Instructions

1. Locate or Create CHANGELOG.md

Check project root for CHANGELOG.md.
If missing, create it with the header:

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

2. Gather Changes

Scan recent work using:

git log --oneline since last tagged version.
tasks/todo.md completed items.
User description of what was shipped.

3. Categorize Changes

Every change goes into exactly one category:

Category	When to Use
Added	New features, new files, new capabilities
Changed	Modifications to existing functionality
Deprecated	Features that will be removed in future versions
Removed	Features that were removed
Fixed	Bug fixes
Security	Vulnerability patches

4. Determine New Version

Automatically invoke the semantic-versioning skill.
Use the categorized changes to determine if the next version should be Major, Minor, or Patch.
Ensure the version is updated in both CHANGELOG.md and .github/repository-metadata.json.

5. Write Entry

## [X.Y.Z] - YYYY-MM-DD

### Added
- Brief description of what was added

### Changed
- Brief description of what changed

### Fixed
- Brief description of what was fixed

6. Rules

Most recent version at the top.
Always include the date in ISO format (YYYY-MM-DD).
One line per change, starting with a verb.
Group related changes under the same category.
Keep an [Unreleased] section at the top for ongoing work.
Never delete old entries.
Synchronization: Always ensure the version number matches between CHANGELOG.md and .github/repository-metadata.json.

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

11d ago First seen · 94 lines · 39 tokens per session scan A 1a50b7f067b7

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository tuliosousapro/SaaS-blueprint (4 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 640 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-31.

Claude Code Git and workflow Releases antigravity antigravity-ide antigravity-skills claude-code-skill claude-skills

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 Skill

When to Use

Reference

Instructions

1. Locate or Create CHANGELOG.md

2. Gather Changes

3. Categorize Changes

4. Determine New Version

5. Write Entry

6. Rules

What this file has done since we first saw it

Other skills, from other repositories

ios-appstore-builder

app-release-manager

changelog-automator

changelog-generator

release-manager

semantic-versioning