changelog-automation
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits
npx skills add vibeeval/vibecosystem --skill changelog-automation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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/
- Conventional Commits
- Type'lar
- Breaking Change
- Semantic Versioning (SemVer)
- Versiyon Artirma Kurallari
- CHANGELOG.md Formati (Keep a Changelog)
- Type -> Section Mapping
- Changelog Olusturma
- Git Log'dan Changelog
- Otomatik Changelog Script
- Release Notes
- GitHub Release Olusturma
- Pre-release
- CI/CD Entegrasyonu
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 if [ -z "$LAST_TAG" ]; then else fi
What does the changelog-automation skill do?
Git history'den otomatik changelog, semantic versioning, release notes, conventional commits
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill changelog-automation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.