agentleFS
Sign inStart free
MuhammadUsmanGMMuhammadUsmanGM/claude-code-best-practices/.claude/skills/changelog/SKILL.md

changelog

Skill105 starsChanged 31 days agoMITView on GitHub

Generate or update CHANGELOG.md with an entry for the unreleased changes since the last git tag. Invoke when the user asks to cut a release, update the changelog, or summarize changes since v-something.

160 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, soak-test and 10 more.

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.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 12 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • CoralGameSkill

    team-polish

    Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

    Also in 14 projects that use this

  • +5 more from lilangMax
  • +3 more from CoralGame

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 149 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read the existing CHANGELOG.md if present.

    line 15
  2. Distinctive:

    Ask the user for the new version number (semver).

    line 17
  3. Distinctive:

    Do not create a git tag. Do not commit.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 149 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

Produce or update CHANGELOG.md in the Keep-a-Changelog format.

Steps

  1. git describe --tags --abbrev=0 to find the most recent tag. If no tag exists, use the repo's first commit and tell the user there's no prior tag.
  2. git log <last-tag>..HEAD --oneline --no-merges to enumerate commits.
  3. Read the existing CHANGELOG.md if present. Match its headings, casing, and date format. If missing, create one with the Keep-a-Changelog header.
  4. Group commits into sections — Added, Changed, Fixed, Removed, Deprecated, Security — by inspecting subject prefixes (feat: → Added, fix: → Fixed, refactor:/perf: → Changed, etc.). Merge trivial commits into one bullet.
  5. Ask the user for the new version number (semver). Do not guess.
  6. Insert a new ## [x.y.z] - YYYY-MM-DD section above the previous release. Move "Unreleased" content in if present.
  7. Show the diff before writing. Write only after confirmation.

Rules

  • Rewrite commit subjects into user-facing language. "feat: add FOO" → "Added FOO that does X."
  • Drop internal-only commits (chore(deps), CI-only changes) unless they affect consumers.
  • Do not create a git tag. Do not commit. Hand the finished file back to the user.

Output

Print the new section you added, then stop.

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