agentleFS
Sign inStart free
WST2002WST2002/claude-code-skills/skills/changelog-writer/SKILL.md

changelog-writer

Skill4 starsChanged 27 days agoMITView on GitHub

Use when writing release notes, a CHANGELOG.md entry, a version summary or "what's new" text from git history, merged pull requests or tickets, or deciding the next semantic version number.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use regex-builder and readme-generator.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jMertaSkill

    regex-builder

    Use when the user asks to create, debug, explain, validate, or optimize a regular expression or replacement for a specific engine. Verifies representative matches, non-matches, captures, escaping, portability limits, and backtracking risk in the target runtime.

    Also in 3 projects that use this

  • glinckerSkill

    readme-generator

    Generates comprehensive README.md files for software projects by analyzing codebase structure

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the existing CHANGELOG.md style: if the project has one.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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

Changelog Writer

Overview

Release notes tell users what changed for them and what they must do. Build them from the real history between two versions, group by impact, and write in the reader's language, not in commit-speak.

Method

  1. Find the range: last release tag to now — git describe --tags --abbrev=0, then git log <tag>..HEAD --oneline --no-merges. With GitHub: gh pr list --state merged --search "merged:>=<date>" or gh release view.
  2. Read each change, not just the subject line, when the impact is unclear (git show <sha> --stat).
  3. Classify each change: Added, Changed, Deprecated, Removed, Fixed, Security (Keep a Changelog). Drop internal-only changes (refactors, CI, tests) unless the audience is developers of the project.
  4. Decide the version (Semantic Versioning): any breaking change → major; new backward-compatible feature → minor; only fixes → patch.
  5. Rewrite for the audience: user-facing benefit first, one line each, link the PR or issue.
  6. Write breaking changes with migration steps.
  7. Follow the existing CHANGELOG.md style if the project has one.

Format

## [2.4.0] - 2026-10-16

### Added
- Export orders to CSV from the Orders page. (#412)

### Changed
- Search now matches partial words. (#405)

### Fixed
- Coupon discount no longer disappears when the cart quantity changes. (#398)

### Security
- Upgrade `jsonwebtoken` to 9.0.2 to fix token verification bypass. (#401)

### Breaking changes
- `GET /api/orders` now returns paginated results. Read items from `data` and
  pass `cursor` to fetch the next page. (#410)

Dates in ISO format. Newest version at the top. Omit empty sections.

Common mistakes

  • Copying commit subjects ("fix stuff", "wip") into release notes.
  • Hiding breaking changes inside "Changed" with no migration steps.
  • Listing internal refactors that users do not care about.
  • Choosing a minor version for a release that breaks clients.
  • Mentioning features from unmerged branches.

Made by Wageesha Tripathi · LinkedIn · Email · More skills

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.

Check your setup, free