Automated summary

This skill keeps the project's CHANGELOG.md accurate and current by drawing on the git history and following Keep a Changelog conventions.

Strengths

Scans the git log since the last changelog entry to surface undocumented changes
Sorts changes into the standard Added, Changed, Fixed, Removed, Security and Deprecated sections
Rewrites raw commit messages into human-readable entries
Handles moving the [Unreleased] section into a dated version on release

Limitations

Entry quality depends on how clear the commit messages and available git history are
Does not infer breaking changes or semver version numbers on its own
Assumes Keep a Changelog Markdown; a changelog in a very different format may need manual adjustment

When to use it

Use it after merging significant PRs or right before a release to bring the CHANGELOG up to date.

When not to use it

Avoid it when the project has no usable git history or relies on a different tool that auto-generates the changelog.

Security analysis

Safe

Quality score82/100

The skill only inspects git history and edits CHANGELOG.md. Bash is declared but used for benign read-only git-log inspection and file editing; there are no destructive commands, network calls, credential handling, or obfuscated payloads. Residual risk is limited to ordinary file modification of the changelog, which is the stated purpose.

No concerns found

How this analysis is made

Examples

Update since last release

/changelog-maintainer update CHANGELOG.md with changes since v1.0.0

Stale changelog fix

Our CHANGELOG is stale — go through the git log since the last entry and add the missing items under [Unreleased].

Cut a release

We're releasing 1.2.0 today: move the [Unreleased] section to [1.2.0] with today's date and keep the existing format.

name: changelog-maintainer description: > Maintain and update the project CHANGELOG.md keeping it current. Invoke for: "keep changelog updated", "CHANGELOG is stale", "changelog maintenance", "update release history", "automate changelog", "add to changelog". argument-hint: version or changes to add to changelog allowed-tools: Read, Write, Edit, Bash

Skill: Changelog Maintainer — Keep History Current

Name: Changelog Maintainer — Keep History Current
Author: Skills Guide Bot

Category: Documentation

Role

Keep CHANGELOG.md accurate, current, and following Keep a Changelog conventions.

When to invoke

After merging significant PRs
Before a release
"CHANGELOG is out of date"

Instructions

Check git log since last changelog entry
Categorize: Added, Changed, Fixed, Removed, Security, Deprecated
Write human-readable entries (not raw commit messages)
Add [Unreleased] section if not present
When releasing: move Unreleased → [version] with date
Keep format consistent with existing entries

Output format

## [Unreleased]
### Added
- New feature X

## [1.1.0] — 2026-03-20
### Fixed
- Bug in Y

Example

/changelog-maintainer update CHANGELOG.md with changes since v1.0.0

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/changelog-maintainer-keep-history-current-mrx3xz4n/download' --output '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md.part' && mv '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md.part' '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md' && test -s '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/changelog-maintainer' && cp -R '.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n' '.claude/skills/changelog-maintainer'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n'

openskills read 'changelog-maintainer-keep-history-current-mrx3xz4n'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/changelog-maintainer-keep-history-current-mrx3xz4n/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544

Skills Guide Bot