agentleFS
Sign inStart free
milad-ahmdmilad-ahmd/agent-skills/skills/changelog-from-git/SKILL.md

changelog-from-git

Skill5 starsChanged 16 days agoMITView on GitHub

Generates polished, human-readable release notes and CHANGELOG entries from a git commit range, grouping changes by impact and crediting contributors. Use when the user asks for release notes, a changelog, "what changed since vX", or to draft a GitHub release.

  • Commits and pushes

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Default range: from the latest tag to HEAD.

    line 19
  2. Very specific:

    When gh is available, enrich entries with PR titles, labels and authors: gh pr list --state merged --search "merged:>=<date>" --json …

    line 20
  3. Distinctive:

    If the commits don't follow Conventional Commits, classify by reading the diff summary, not just the message.

    line 33
  4. Distinctive:

    Every breaking change gets migration steps.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Changelog from Git

Release notes for humans, not a dump of commit messages.

1. Determine the range

git describe --tags --abbrev=0                 # latest tag
git tag --sort=-creatordate | head -5
git --no-pager log <from>..<to> --no-merges --pretty='%h|%an|%s'
git --no-pager log <from>..<to> --merges --pretty='%h|%s'   # PR merges (#123)

Default range: from the latest tag to HEAD. If there are no tags, use the whole history and say so. When gh is available, enrich entries with PR titles, labels and authors: gh pr list --state merged --search "merged:>=<date>" --json number,title,author,labels.

2. Classify

SectionSources
⚠️ Breaking changes!, BREAKING CHANGE, removed or renamed public APIs, config changes
✨ Featuresfeat
🐛 Fixesfix
⚡ Performanceperf
📚 Docs / 🧹 Maintenancedocs, refactor, chore, build, ci, deps (collapse these)

If the commits don't follow Conventional Commits, classify by reading the diff summary, not just the message.

3. Write

## v1.4.0 — 2026-10-25

**Highlights:** one or two sentences a user cares about.

### ⚠️ Breaking changes
- `config.timeout` is now in milliseconds. **Migration:** multiply existing values by 1000. (#142)
### ✨ Features
- Export reports as CSV (#138, @alice)
### 🐛 Fixes
- Fix crash when the profile picture is missing (#140)

**Full diff:** https://github.com/OWNER/REPO/compare/v1.3.0...v1.4.0

Rules

  • Rewrite each entry from the user's point of view ("Fix crash when...", not "fix null check in UserCard").
  • Drop noise: merge commits, typo fixes, version bumps, "wip".
  • Every breaking change gets migration steps.
  • Suggest the next version number using SemVer (major for breaking changes, minor for features, patch for fixes only).
  • Prepend the entry to CHANGELOG.md (Keep a Changelog style) only if asked. Create a GitHub release with gh release create only after the user confirms.

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