agentleFS
Sign inStart free
eigent-aieigent-ai/agent-skills/skills/git-and-github/changelog-generator/SKILL.md

changelog-generator

Skill27 starsChanged 8 months agoApache-2.0View on GitHub

Transform git commit history into polished user-facing changelogs and release notes. Use when the user wants a CHANGELOG.md from a version tag or date range, weekly product updates, app store release notes, or Keep a Changelog formatted output with internal noise filtered out.

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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 93 edited versions we read keep these.

  • 4

    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:

    Create release notes from commits in the past 7 days.

    line 45
  2. Distinctive:

    Write app store release notes for iOS v3.2 since the last tag.

    line 46
  3. Distinctive:

    If the user provides a style guide file, enforce:

    line 52
  4. Distinctive:

    Run git log in the correct repo root — confirm with user if ambiguous.

    line 61
  5. Distinctive:

    Do not invent features not present in commits.

    line 62

“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

Scans commits across a date range or version tag, categorizes changes, strips internal noise, and rewrites technical language into plain prose.

Source Repository

/changelog

Point at a commit range, version tag, or time window.

Workflow:

  1. Gather commits via git log for the requested range.
  2. Filter out internal noise — refactors, test-only, CI/chore commits unless user wants them.
  3. Group by type: New Features, Improvements, Bug Fixes, Security.
  4. Rewrite each entry in user-facing language (benefits, not implementation details).
  5. Format per Keep a Changelog or the user's style guide if provided.
  6. Output ready-to-commit CHANGELOG.md or alternate format (Notion post, app store notes).

Grouping rules:

Commit signalCategory
feat:, new capabilityNew Features
fix:, regressionBug Fixes
perf:, refactor: (user-visible)Improvements
security:, CVE, auth fixSecurity
chore:, ci:, test:Filter out (default)

Example Prompts

  • Generate a changelog for commits between v1.4.0 and v1.5.0. Group by features, improvements, bug fixes, security. User-facing language.
  • Create release notes from commits in the past 7 days. Filter chore/ci/test. Output as a Notion-ready product update post.
  • Write app store release notes for iOS v3.2 since the last tag. Max 200 words. Friendly and benefit-focused.

Style Guide Support

If the user provides a style guide file, enforce:

  • Terminology (feature names, product voice)
  • Tone (formal vs casual)
  • Formatting (bullet vs paragraph, emoji policy)

Guardrails

  • Run git log in the correct repo root — confirm with user if ambiguous.
  • Do not invent features not present in commits.
  • Flag breaking changes explicitly in a dedicated section.
  • For app store notes, respect platform character limits.

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