Git history'den otomatik changelog, semantic versioning, release notes, conventional commits
npx skills add https://github.com/vibeeval/vibecosystem --skill changelog-automation
Commit mesajlari bu formatta olmali:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
| 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 |
feat(api)!: remove deprecated endpoints
BREAKING CHANGE: /v1/users endpoint kaldirildi, /v2/users kullanin
! isareti veya BREAKING CHANGE: footer'i = MAJOR versiyon artisi.
MAJOR.MINOR.PATCH
MAJOR: Breaking change (geriye uyumsuz)
MINOR: Yeni ozellik (geriye uyumlu)
PATCH: Bug fix (geriye uyumlu)
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
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
| 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 |
# 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)"
# 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/^- [^:]*: /- /'
# 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"
gh release create "v2.0.0-beta.1" --prerelease --title "v2.0.0 Beta 1" --notes "..."
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 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 formatini dogrulama kurallari:
## [X.Y.Z] - YYYY-MM-DDchangelog-on-release.ts Stop hook'u session sonunda:
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).
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.
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
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).
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.
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.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
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
Take vibeeval/changelog-automation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.