mcpbeat Sign in

Changelog Automation Agent Skill

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

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
521
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/vibeeval/vibecosystem --skill changelog-automation

The instruction itself

19 sections, as written by the author

Changelog Automation

Conventional Commits

Commit mesajlari bu formatta olmali:

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

[optional body]

[optional footer(s)]

Type'lar

| Type | Aciklama | SemVer Etkisi |

|------|---------|---------------|

| feat | Yeni ozellik | MINOR |

| fix | Bug fix | PATCH |

| docs | Dokumantasyon | - |

| style | Formatting (kod degisikligi yok) | - |

| refactor | Kod degisikligi (feature/fix degil) | - |

| perf | Performans iyilestirme | PATCH |

| test | Test ekleme/duzeltme | - |

| chore | Build, CI, tooling | - |

| ci | CI/CD degisikligi | - |

| build | Build sistemi degisikligi | - |

| revert | Geri alma | PATCH |

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)

# 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 Type | Changelog Section |

|-------------|------------------|

| feat | Added |

| fix | Fixed |

| perf | Changed |

| refactor | Changed |

| docs | - (changelog'a eklenmez) |

| style | - |

| test | - |

| chore | - |

| BREAKING CHANGE | Removed / Changed (breaking note ile) |

| security fix | Security |

| deprecation | Deprecated |

Changelog Olusturma

Git Log'dan Changelog

# 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

# 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

# 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

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

CI/CD Entegrasyonu

GitHub Actions Changelog

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

# 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

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take vibeeval/changelog-automation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.