agentleFS
stijnvanhullestijnvanhulle/agents/.agents/skills/changelog/SKILL.md

changelog

Skill2 starsChanged 56 days agoMITView on GitHub

Turns commit history and changesets into user-facing release notes. Use when preparing a release, writing or updating a changelog, or asked what changed in a version.

165 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 13 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 10 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 10 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • +6 more from lilangMax
  • +2 more from CoralGame

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read the git history for the range and the changesets released in it.

    line 13
  2. Very specific:

    Write each entry for the person upgrading, in the documentation voice.

    line 24

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

Turn commits and changesets into entries a package user can act on. Follow the repo's docs/changelog.md when it exists, otherwise references/format.md.

1. Collect

Read the git history for the range and the changesets released in it. For a release not yet cut, include the pending .changeset/*.md files. Fetch remote tags when none exist locally.

2. Group

Sort entries into features and improvements, bug fixes, and breaking changes. Drop refactor, test, and chore commits unless a changeset carries them. List dependency bumps under Dependencies, or drop them when users see no change, and say which you did.

3. Translate

Write each entry for the person upgrading, in the documentation voice. Lead with what they get, and name the real option, export, or command. The entries come from changesets, so a weak entry is fixed in its changeset with the changeset skill.

Output

One ## <version> section, where the version is the last tag plus the highest pending bump, with a ### block per change type that has entries and one line per entry. Skip the per-package #### level when all packages share one version. End with one line naming what you dropped as noise.

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.