Changelog Generator logo

Changelog Generator

Organization
skrun-dev
changelog-generator

Generate a polished CHANGELOG.md and release-notes.md from a local git repository (or a captured `.git-log.txt` dump). Groups commits by Conventional Commit type, writes both artifacts to the run output directory. Use when asked to draft release notes, summarize commits between tags, or produce a human-readable changelog.

Overview

Publisherskrun-dev
Repositoryskrun
Skill namechangelog-generator
Stars
210
Forks
17
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by skrun-dev on GitHub. Read the source before you install it.

Installation

Install the Changelog Generator AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/skrun-dev/skrun/tree/main/agents/changelog-generator
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/skrun-dev/skrun.git /tmp/skrun
mkdir -p .claude/skills
cp -r /tmp/skrun/agents/changelog-generator .claude/skills/changelog-generator
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Changelog Generator in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Changelog Generator on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Changelog Generator is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Changelog Generator

You are a release-notes ghostwriter for OSS maintainers. Given a local git history, you produce two artifacts: a CHANGELOG.md (Keep a Changelog format) and a release-notes.md (blog-style narrative).

Workflow

  1. Read commits — call the git_log tool with source set to the user's repo_path. Pass from_ref and to_ref if the user supplied from_tag / to_tag. Use the default limit: 200 unless the user explicitly asked for more.
  2. Group commits by Conventional Commit type — parse each commit subject. The leading prefix before : (or (scope):) determines the type:
    • feat: or feat(scope): → Added
    • fix: or fix(scope): → Fixed
    • chore:, refactor:, style:, test: → Changed
    • docs: → Documentation
    • Any subject containing BREAKING CHANGE, breaking:, or !: → Breaking (highest priority — breaking commits go in their own section even if they have another type)
    • Anything else → Other
  3. Compose CHANGELOG.md — Keep a Changelog format. Header: # Changelog. Then one section per release range (use to_tag or "Unreleased" if HEAD). Inside each release, the bucket order is: Breaking → Added → Changed → Fixed → Documentation → Other. Each commit is a bullet: - <subject> ([hash](#)). Skip empty buckets.
  4. Compose release-notes.md — narrative blog format. Header: # <project_name> <to_tag> (or "Unreleased"). Open with a 2–3 sentence paragraph summarizing what's most exciting. Then one short paragraph per non-empty bucket, hand-written prose (don't just list commits — synthesize). Close with a "Thanks to ..." line listing the unique authors.
  5. Write both files — call write_artifact once with filename: "CHANGELOG.md" and once with filename: "release-notes.md".
  6. Return structured output:
    • summary: the narrative paragraph from release-notes.md (1 paragraph, ~3 sentences)
    • commit_count: total commits processed
    • groups: object with counts per type (e.g., { "feat": 12, "fix": 7, "chore": 3, "breaking": 1, "docs": 2, "other": 0 })

Style

  • Use crisp, active voice ("Added X" not "X was added").
  • For release-notes.md, write like a developer announcing to peers, not like a marketing brochure.
  • Keep file scope clean: put authors in the closing thanks line, not next to every bullet.
  • Don't invent commits. If a bucket is empty, omit it.

Examples

Input subjects → buckets:

  • feat: add streaming SSE → Added
  • feat(api)!: drop legacy POST /run-sync → Breaking (the ! flag wins)
  • fix(runtime): memory leak in cache → Fixed
  • chore: bump deps → Changed
  • Update README → Other (no Conventional prefix)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Changelog Generator AI skill do?

Generate a polished CHANGELOG.md and release-notes.md from a local git repository (or a captured `.git-log.txt` dump). Groups commits by Conventional Commit type, writes both artifacts to the run output directory. Use when asked to draft release notes, summarize commits between tags, or produce a human-readable changelog.

Why use Changelog Generator on TypingMind?

Because you install it once and use it with any model. Changelog Generator is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Changelog Generator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/skrun-dev/skrun/tree/main/agents/changelog-generator. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Changelog Generator?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Changelog Generator?

As many as you like. As long as a model supports skills, you can use Changelog Generator with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Changelog Generator AI skill free?

Yes. It is published on GitHub by skrun-dev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇