Changelog Automation logo

Changelog Automation

Community
vibeeval
changelog-automation

Git history'den otomatik changelog, semantic versioning, release notes, conventional commits

Overview

Publishervibeeval
Repositoryvibecosystem
Skill namechangelog-automation
Stars
533
Forks
44
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vibeeval on GitHub. Read the source before you install it.

Installation

Install the Changelog Automation 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/vibeeval/vibecosystem/tree/main/skills/changelog-automation
  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/vibeeval/vibecosystem.git /tmp/vibecosystem
mkdir -p .claude/skills
cp -r /tmp/vibecosystem/skills/changelog-automation .claude/skills/changelog-automation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Changelog Automation 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 Automation 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 Automation 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 Automation

Conventional Commits

Commit mesajlari bu formatta olmali:

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Type'lar

TypeAciklamaSemVer Etkisi
featYeni ozellikMINOR
fixBug fixPATCH
docsDokumantasyon-
styleFormatting (kod degisikligi yok)-
refactorKod degisikligi (feature/fix degil)-
perfPerformans iyilestirmePATCH
testTest ekleme/duzeltme-
choreBuild, CI, tooling-
ciCI/CD degisikligi-
buildBuild sistemi degisikligi-
revertGeri almaPATCH

Breaking Change

feat(api)!: remove deprecated endpoints

BREAKING CHANGE: /v1/users endpoint kaldirildi, /v2/users kullanin

! isareti veya BREAKING CHANGE: footer'i = MAJOR versiyon artisi.

Semantic Versioning (SemVer)

MAJOR.MINOR.PATCH

MAJOR: Breaking change (geriye uyumsuz)
MINOR: Yeni ozellik (geriye uyumlu)
PATCH: Bug fix (geriye uyumlu)

Versiyon Artirma Kurallari

Commit'lerde BREAKING CHANGE varsa → MAJOR++
Commit'lerde feat varsa → MINOR++
Sadece fix/perf/refactor varsa → PATCH++
Sadece docs/style/test/chore varsa → versiyon artmaz

CHANGELOG.md Formati (Keep a Changelog)

markdown
# Changelog

All notable changes to this project will be documented in this file.

## [Unreleased]

## [1.2.0] - 2026-03-25

### Added
- Yeni ozellik aciklamasi (#123)

### Changed
- Degisiklik aciklamasi (#124)

### Deprecated
- Kaldirilacak ozellik uyarisi

### Removed
- Kaldirilan ozellik

### Fixed
- Bug fix aciklamasi (#125)

### Security
- Guvenlik duzeltmesi

## [1.1.0] - 2026-03-20

### Added
- ...

[Unreleased]: https://github.com/user/repo/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/user/repo/compare/v1.1.0...v1.2.0
[1.1.0]: https://github.com/user/repo/releases/tag/v1.1.0

Type -> Section Mapping

Commit TypeChangelog Section
featAdded
fixFixed
perfChanged
refactorChanged
docs- (changelog'a eklenmez)
style-
test-
chore-
BREAKING CHANGERemoved / Changed (breaking note ile)
security fixSecurity
deprecationDeprecated

Changelog Olusturma

Git Log'dan Changelog

bash
# Son tag'den bu yana commit'ler
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"%s" --no-merges

# Tum tag'ler arasi
git log v1.0.0..v1.1.0 --pretty=format:"- %s (%h)" --no-merges

# Conventional commit parse
git log --pretty=format:"%s" | grep -E "^(feat|fix|refactor|perf|docs|test|chore|ci|build)"

Otomatik Changelog Script

bash
# Son release'den bu yana degisiklikleri kategorize et
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")

if [ -z "$LAST_TAG" ]; then
  RANGE="HEAD"
else
  RANGE="${LAST_TAG}..HEAD"
fi

echo "## [Unreleased]"
echo ""

echo "### Added"
git log $RANGE --pretty=format:"- %s" --no-merges | grep "^- feat" | sed 's/^- feat[^:]*: /- /'

echo ""
echo "### Fixed"
git log $RANGE --pretty=format:"- %s" --no-merges | grep "^- fix" | sed 's/^- fix[^:]*: /- /'

echo ""
echo "### Changed"
git log $RANGE --pretty=format:"- %s" --no-merges | grep -E "^- (refactor|perf)" | sed 's/^- [^:]*: /- /'

Release Notes

GitHub Release Olusturma

bash
# Changelog'dan release notes
VERSION="v1.2.0"
NOTES=$(cat <<'EOF'
## What's New

### Features
- Feature 1 description
- Feature 2 description

### Bug Fixes
- Fix 1 description

### Breaking Changes
- Breaking change description

**Full Changelog**: https://github.com/user/repo/compare/v1.1.0...v1.2.0
EOF
)

gh release create "$VERSION" --title "$VERSION" --notes "$NOTES"

Pre-release

bash
gh release create "v2.0.0-beta.1" --prerelease --title "v2.0.0 Beta 1" --notes "..."

CI/CD Entegrasyonu

GitHub Actions Changelog

yaml
name: Release
on:
  push:
    tags: ['v*']

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0

      - name: Generate changelog
        run: |
          PREV_TAG=$(git describe --tags --abbrev=0 HEAD^ 2>/dev/null || echo "")
          if [ -n "$PREV_TAG" ]; then
            git log ${PREV_TAG}..HEAD --pretty=format:"- %s" --no-merges > RELEASE_NOTES.md
          fi

      - name: Create Release
        uses: softprops/action-gh-release@v1
        with:
          body_path: RELEASE_NOTES.md

Breaking Change Tespiti

bash
# Breaking change iceren commit'leri bul
git log --pretty=format:"%H %s" | grep -i "breaking\|BREAKING CHANGE\|!"

# feat! veya fix! formatinda
git log --pretty=format:"%s" | grep -E "^(feat|fix|refactor)!"

Changelog Validation

Changelog formatini dogrulama kurallari:

  • Her version header'i tarih icermeli: ## [X.Y.Z] - YYYY-MM-DD
  • Section'lar dogru sirayla: Added, Changed, Deprecated, Removed, Fixed, Security
  • Bos section olmamali
  • Link referanslari dosya sonunda olmali
  • Unreleased section en ustte olmali

Session Changelog Hook

changelog-on-release.ts Stop hook'u session sonunda:

  • Session'da yapilan commit'leri otomatik toplar
  • Conventional commit formatinda parse eder
  • Ozet changelog gosterir

Frequently asked questions

What does the Changelog Automation AI skill do?

Git history'den otomatik changelog, semantic versioning, release notes, conventional commits

Why use Changelog Automation on TypingMind?

Because you install it once and use it with any model. Changelog Automation 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 Automation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vibeeval/vibecosystem/tree/main/skills/changelog-automation. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Changelog Automation?

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 Automation?

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

Is the Changelog Automation AI skill free?

Yes. It is published on GitHub by vibeeval 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 👇