agentleFS
Sign inStart free
Lethe044Lethe044/agentskill-kit/skills/changelog-generator/SKILL.md

changelog-generator

Skill48 starsChanged 17 days agoMITView on GitHub

Turns git log output into a grouped markdown changelog using conventional commit prefixes such as feat, fix and docs. Use when the user prepares a release, asks for release notes, or wants a summary of what changed between two tags.

99 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use api-test-suite-builder, fda-consultant-specialist 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.
  • Arnav-0Skill

    api-test-suite-builder

    Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    Also in 7 projects that use this

  • Hussain-ElfalahSkill

    fda-consultant-specialist

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 5 projects that use this

  • Hussain-ElfalahSkill

    quality-manager-qmr

    Also in 5 projects that use this

  • csiddhant796-blipSkill

    self-eval

    Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.

    Also in 6 projects that use this

  • ComposioHQSkill

    meeting-notes-and-actions

    Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.

    Also in 4 projects that use this

  • +4 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 93 edited versions we read keep these.

  • 2

    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 the draft once, merge duplicate lines, and rewrite subjects that only make sense to the author.

    line 40
  2. Distinctive:

    Add a short summary paragraph on top for releases with user visible changes.

    line 41

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

Groups commit subjects by type so release notes can be written in minutes.

When to use

  • The user is cutting a release and needs notes.
  • The user asks what changed since the last tag.
  • A pull request needs a summary of its commits.

How to run

Pipe git log with the %h|%s format into the script:

git log v1.0.0..HEAD --pretty=format:"%h|%s" | python scripts/make_changelog.py --title "v1.1.0"

Without a title, the heading is Changelog.

Output

Markdown on standard output. Sections appear in a fixed order: Breaking changes, Features, Fixes, Performance, Documentation, Refactoring, Tests, Build and CI, Other. Empty sections are left out. A ! after the type (feat!:) or a BREAKING CHANGE marker puts the commit under Breaking changes. Each line shows the scope in bold, the subject and the short hash.

After running

Read the draft once, merge duplicate lines, and rewrite subjects that only make sense to the author. Add a short summary paragraph on top for releases with user visible changes.

Errors

Empty input prints a heading and the line No commits found.. Lines without a | separator are ignored.

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