Przejdź do treści
Biblioteka skilli
DevOps i chmura · Pisanie

release-notes

/release-notes

Szkicuje notatki i sekcję CHANGELOG.md od ostatniego tagu, grupując zmiany w kategorie i linkując PR oraz commity.

Repozytorium
claude-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/release-notes.mjs

Co robi i kiedy

Szkicuje notatki i sekcję CHANGELOG.md od ostatniego tagu, grupując zmiany w kategorie i linkując PR oraz commity.

Wyzwalacze z opisu

AddFixRemove
Oryginalny opis (EN)

Draft release notes and a Keep-a-Changelog CHANGELOG.md section from git history — last tag..HEAD by default, grouped into Breaking/Added/Changed/Fixed/Removed/Security/Docs from Conventional Commits or, for free-form messages, from the first word ("Add", "Fix", "Remove"…); skips merges, wip, fixup! and version-bump commits, merges duplicate subjects, links PR/MR numbers and commit SHAs for GitHub and GitLab remotes, lists authors and Co-authored-by contributors, and suggests the next semver bump. Use when cutting a release, writing a GitHub release body, or starting or updating a CHANGELOG.

Jak działa

  1. What it does
  2. How Claude should use it
  3. Limits
Sekcje z nagłówków SKILL.md, w oryginale · 35 linii, 592 słów
Podgląd SKILL.md
---
name: release-notes
description: Draft release notes and a Keep-a-Changelog CHANGELOG.md section from git history — last tag..HEAD by default, grouped into Breaking/Added/Changed/Fixed/Removed/Security/Docs from Conventional Commits or, for free-form messages, from the first word ("Add", "Fix", "Remove"…); skips merges, wip, fixup! and version-bump commits, merges duplicate subjects, links PR/MR numbers and commit SHAs for GitHub and GitLab remotes, lists authors and Co-authored-by contributors, and suggests the next semver bump. Use when cutting a release, writing a GitHub release body, or starting or updating a CHANGELOG.
---

# release-notes

`scripts/release-notes.mjs` is zero-dependency Node 22+. It only reads git, except with `--write`. It never creates tags, commits or pushes.

```
node release-notes.mjs                                  # last tag..HEAD, printed
node release-notes.mjs --version 1.4.0                  # header ## [1.4.0] - today (default: ## [Unreleased])
node release-notes.mjs --from v1.2.0 --to v1.3.0
node release-notes.mjs --format github --version 1.4.0  # GitHub release body + "Full Changelog" compare link
node release-notes.mjs --version 1.4.0 --changelog CHANGELOG.md --write
node release-notes.mjs --cwd path/to/repo --repo-url none
```

The notes go to stdout; a summary goes to stderr: range, kept/skipped counts, commit style detected, link base, groups, and the **suggested bump** (major if anything is breaking, minor if anything was added, else patch, computed from the last semver tag).

## What it does
- **Range:** the latest tag reachable from `--to` up to `--to`. If `--to` is itself tagged, it describes that tag (previous tag..tag) and uses its version. No tags: the whole history, and it says so.
- **Grouping:** `feat` → Added, `fix` → Fixed, `perf` → Performance, `refactor` → Changed, `docs`, `test`, `build`/`ci`, `chore`. `type!:` or a `BREAKING CHANGE:` footer → Breaking, with the footer text under the bullet. Free-form subjects are grouped by their first word (Add/New → Added, Fix → Fixed, Remove/Delete/Drop → Removed, Update/Improve/Refactor/Rename → Changed, Docs/README → Docs); anything else lands in Changed. A leading `area: ` becomes a bold scope.
- **Skipped:** merge commits, `wip`, `fixup!`/`squash!`, "Initial commit", and subjects that are only a version (`v1.0.1`, `Bump version to 1.0.0`, `chore(release): 1.2.1`). Identical subjects are listed once.
- **Links:** from `git remote get-url origin` (https, ssh and `git@host:` forms; credentials in the URL are dropped). GitHub: `#12` → `/pull/12`. GitLab: `!7` → merge request, `#7` → issue. Other hosts get plain text.
- **`--write`:** inserts the section into the changelog below `[Unreleased]` and above the newest version, creating the file with the standard Keep-a-Changelog header if missing. It refuses if that version is already present (so re-running is a no-op), regenerates an existing `[Unreleased]` section in place, and saves `CHANGELOG.md.bak` before changing anything.

## How Claude should use it
1. Run it without `--write` and read the summary. Confirm the range and the version with the user; offer the suggested bump.
2. **Rewrite the bullets for users.** The output is commit subjects, which describe what the developer did. Turn them into what changed for the person using the project: merge related commits into one bullet, drop internal noise (refactors, CI, tests, typo fixes) unless it affects users, explain breaking changes with what to do about them, and keep the PR/commit links. Don't invent changes that aren't in the commits.
3. Show the rewritten section. Only after the user agrees, write it: run with `--write` to create the section, then edit the bullets in the file (or paste the rewritten text directly).
4. Tagging and publishing are the user's call. Give them the commands (`git tag v1.4.0 && git push origin v1.4.0`, `gh release create v1.4.0 --notes-file …`); don't run them.

## Limits
- It sees commit messages only. Squash-merged PRs show their squash subject; a PR merged with a merge commit shows its individual commits, and the merge commit (with the PR number) is skipped, so those bullets have no PR link.
- First-word grouping is a guess. "Make X faster" goes to Changed, "Handle Y" to Fixed. That is why step 2 exists.
- Contributors are git author names, not GitHub usernames, so there are no `@mentions`.
- Release date is today (override with `--date YYYY-MM-DD`). No compare-link references are added at the bottom of CHANGELOG.md.
Pliki w paczce (2)
  • SKILL.md 4 KB
  • scripts/release-notes.mjs 14 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · binay-py/claude-skills100MIT
mono/SkiaSharp100MIT
niekcandaele/claude-helpers100MIT
kenryu42/cc-safety-net100MIT
zeitlos/lucity100AGPL-3.0
openshift-pipelines/pipelines-as-code100Apache-2.0
paperwingio/paperwing100Apache-2.0
jelvodev/yaap100MIT
yearzen1/LocalSkillManager100MIT

Migawka bazy z 13.11.2026 · wersja paczki 76eab64f76bf (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100changelog
    Pisze notatki do wydania i wpis w CHANGELOG.md na podstawie historii gita od ostatniego tagu.
  • 90changelog
    Generuje lub aktualizuje CHANGELOG.md z commitów konwencjonalnych od ostatniego tagu, grupując zmiany w Added, Changed, Fixed i innych sekcjach.
  • 100changelog-generator
    Generuje lub aktualizuje CHANGELOG.md w formacie Keep a Changelog z historii gita, grupując commity w sekcje Added, Changed, Fixed, Security i inne, oraz rekomenduje podniesienie wersji.
  • 95prepare-release
    Automatyzuje całe wydanie: czyta commity od ostatniego tagu, wylicza podbicie semver, pisze changelog, tworzy i scala PR wydania, czeka na zielone CI, taguje i śledzi build Dockera.
  • 100changelog-keeper
    Prowadzi czytelny CHANGELOG.md w formacie Keep a Changelog, proponuje kolejną wersję semver i szkicuje notatki wydania.
  • 100chamoji-release
    Wydaje wersję z historii gita jednym poleceniem: dobiera podbicie semver, dopisuje CHANGELOG i tworzy commit z tagiem.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.