agentleFS
kellykampenkellykampen/agent-skills/skills/engineering/add-to-changelog/SKILL.md

add-to-changelog

Skill2 starsChanged 15 days agoMITView on GitHub

Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning. Use when the user asks to "add a changelog entry", "update the changelog", "log this change", or runs /add-to-changelog with a version, change type, and message. Creates CHANGELOG.md if missing, adds the entry under the right version + change-type section, and keeps formatting consistent.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning.

    line 15
  2. Distinctive:

    If any argument is missing, infer sensible values from context (e.g.

    line 23
  3. Very specific:

    Check if CHANGELOG.md exists in the project root.

    line 28
  4. Very specific:

    Look for an existing ## [<version>] section.

    line 37
  5. Very specific:

    If it exists, add the entry under the appropriate ### <Change Type> heading (create the heading if absent).

    line 38
  6. Very specific:

    If it doesn't, create a new version section with today's date: ## [<version>] - YYYY-MM-DD (get the date from date +%F), then the …

    line 39
  7. Distinctive:

    Keep versions in reverse-chronological order and entries tidy.

    line 40
  8. Distinctive:

    Write the file back.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add to Changelog

Add a new entry to the project's CHANGELOG.md following the Keep a Changelog format and Semantic Versioning.

Arguments

  • <version> — SemVer version (e.g. 1.1.0, 2.0.0-beta.1)
  • <change_type> — one of: added, changed, deprecated, removed, fixed, security
  • <message> — description of the change (quote multi-word messages)

If any argument is missing, infer sensible values from context (e.g. the current work) or ask the user.

Process

  1. Parse the version, change type, and message from the arguments.
  2. Check if CHANGELOG.md exists in the project root. If not, create it with the standard Keep a Changelog 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/),
    and this project adheres to [Semantic Versioning](https://semver.org/).
  3. Look for an existing ## [<version>] section.
    • If it exists, add the entry under the appropriate ### <Change Type> heading (create the heading if absent).
    • If it doesn't, create a new version section with today's date: ## [<version>] - YYYY-MM-DD (get the date from date +%F), then the change-type heading and entry.
  4. Keep versions in reverse-chronological order and entries tidy.
  5. Write the file back.

Change types

  • Added — new features
  • Changed — changes to existing functionality
  • Deprecated — soon-to-be-removed features
  • Removed — removed features
  • Fixed — bug fixes
  • Security — security fixes

Example

/add-to-changelog 1.1.0 added "Waitlist referral source configuration" →

## [1.1.0] - 2026-01-15

### Added

- Waitlist referral source configuration

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.