agentleFS
Sign inStart free
itsryanarmaniitsryanarmani/skills/changelog/SKILL.md

changelog

Skill1 starsChanged 5 days agoMITView on GitHub

Auto-generate a changelog from git commits since the last tag or specified ref

  • Commits and pushes

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, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 148 edited versions we read keep these.

  • 3

    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:

    Read each commit message and classify into categories:

    line 34
  2. Distinctive:

    Commit messages should be descriptive for best results

    line 89
  3. Distinctive:

    If commits follow conventional format (feat:, fix:, etc.), classification is more accurate

    line 90

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

Generate a grouped changelog from git history.

Arguments

  • $ARGUMENTS - Optional: git ref to start from (tag, commit, branch). Defaults to the most recent tag.

Steps

1. Determine the starting point

# Use argument or find last tag
SINCE="${ARGUMENTS:-$(git describe --tags --abbrev=0 2>/dev/null || echo 'HEAD~50')}"
echo "Generating changelog since: $SINCE"

2. Gather commits

git log "$SINCE"..HEAD --oneline --no-merges

3. Classify commits

Read each commit message and classify into categories:

  • Features: New functionality (keywords: add, implement, create, introduce, support)
  • Fixes: Bug fixes (keywords: fix, resolve, correct, patch, repair)
  • Improvements: Enhancements (keywords: improve, update, enhance, optimize, refactor)
  • Docs: Documentation (keywords: doc, readme, comment)
  • Chores: Maintenance (keywords: chore, ci, build, deps, config, cleanup)
  • Breaking: Breaking changes (keywords: breaking, remove, deprecate, drop)

4. Generate changelog

Format as markdown:

# Changelog

## [Unreleased] — YYYY-MM-DD

### Breaking Changes

- Description of breaking change (commit-hash)

### Features

- Description of new feature (commit-hash)

### Fixes

- Description of bug fix (commit-hash)

### Improvements

- Description of improvement (commit-hash)

### Documentation

- Description of doc change (commit-hash)

### Chores

- Description of maintenance task (commit-hash)

---

Generated from N commits since TAG

5. Output

  • Print the changelog to the conversation
  • Optionally write to CHANGELOG.md if user requests
  • Can also be used as input for gh release create

Notes

  • Commit messages should be descriptive for best results
  • If commits follow conventional format (feat:, fix:, etc.), classification is more accurate
  • For releases: pipe output to gh release create vX.Y.Z --notes-file -

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