Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

technical-writer-release-notes

/technical-writer-release-notes

Pisze notatki wydania i changelog pogrupowane w Added, Changed, Fixed, Deprecated, Removed i Security, z ostrzeżeniami o zmianach niekompatybilnych.

Repozytorium
guild ↗
Licencja
MIT
Ostatnia zmiana repozytorium
26.10.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
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

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

Co robi i kiedy

Pisze notatki wydania i changelog pogrupowane w Added, Changed, Fixed, Deprecated, Removed i Security, z ostrzeżeniami o zmianach niekompatybilnych.

Wyzwalacze z opisu

write the release notes for v2.4draft the changelog entry for this releasedocument whatwrite the upgrade notes for the breaking change in Xsummarize this PR set into release notes
Oryginalny opis (EN)

Authors release notes / changelog entries for a version — grouped as Added / Changed / Fixed / Deprecated / Removed / Security, with breaking-change callouts and upgrade notes. Pulled by the `technical-writer` specialist. TRIGGER: "write the release notes for v2.4", "draft the changelog entry for this release", "document what's new in version Y", "write the upgrade notes for the breaking change in X", "summarize this PR set into release notes". DO NOT TRIGGER for: marketing launch announcements (use `marketing-launch-plan`), blog posts about a release (use `copywriter-long-form`), API referenc

Jak działa

  1. What you do
  2. Output shape
  3. Anti-patterns
  4. Handoff
Sekcje z nagłówków SKILL.md, w oryginale · 54 linii, 360 słów
Podgląd SKILL.md
---
name: technical-writer-release-notes
description: Authors release notes / changelog entries for a version — grouped as Added / Changed / Fixed / Deprecated / Removed / Security, with breaking-change callouts and upgrade notes. Pulled by the `technical-writer` specialist. TRIGGER: "write the release notes for v2.4", "draft the changelog entry for this release", "document what's new in version Y", "write the upgrade notes for the breaking change in X", "summarize this PR set into release notes". DO NOT TRIGGER for: marketing launch announcements (use `marketing-launch-plan`), blog posts about a release (use `copywriter-long-form`), API reference updates (use `technical-writer-api-docs`), user manual updates (use `technical-writer-user-manual`), tutorial updates (use `technical-writer-tutorial`), social post announcing the release (social-media-platform-post).
when_to_use: The parent `technical-writer` specialist pulls this skill when the task is producing a changelog or release-notes page for a specific version. Also fires on explicit user request.
type: specialist
---

# technical-writer-release-notes

Match commit/PR facts exactly, don't rewrite adjacent versions' notes, evidence = a changelog a user on the previous version can upgrade from without surprise.

## What you do

Turn a set of merged changes into a version entry the reader can skim, filter, and act on. Release notes are for humans upgrading — not for marketing, not for internal brag-lists.

- Group entries by type — Added, Changed, Fixed, Deprecated, Removed, Security — in that order. Keep-a-Changelog conventions are fine.
- One bullet per change. Start with a verb, name the surface, link to PR/issue, link to docs if it's a new feature.
- Breaking changes get a top-of-release callout with migration steps or a pointer to a migration guide.
- Deprecations state the replacement and the removal target version.
- Security fixes get a line even when embargoed — credit reporters if agreed.
- Pull from merged PRs, conventional-commit titles, and the milestone. Ask the owning specialist to verify ambiguous entries.

## Output shape

Markdown appended to `CHANGELOG.md` or a version page:

```
## [2.4.0] - 2026-04-24

### Breaking changes
- `POST /orders` now requires `idempotencyKey` header. [migration](./migrations/2.4.md)

### Added
- Webhook retries with exponential backoff. (#1234)

### Changed
- Default page size raised from 25 to 50. (#1240)

### Fixed
- Fixed crash when exporting empty workspace. (#1241)

### Deprecated
- `GET /v1/users/me`; use `GET /v1/session` (removal in 3.0).
```

Store at `.guild/runs/<run-id>/docs/release-<version>.md` if tracked; otherwise patch `CHANGELOG.md` or the release-notes page.

## Anti-patterns

- Internal jargon: "refactored the WidgetFooBar factory" — rewrite for the user-visible outcome or drop it.
- Missing breaking-change callouts — upgrade bricks happen here.
- Marketing speak: "we're thrilled to announce" belongs in the launch post, not the changelog.
- Copy-pasting commit messages verbatim (`fix: wtf`).
- No PR/issue links — the reader can't dig in when a line affects them.
- One-line "various fixes and improvements" — users cannot plan upgrades against vapor.

## Handoff

Return the release-notes path/diff to the invoking `technical-writer` specialist. If a change warrants more coverage, chain into `copywriter-long-form` (blog post) or `marketing-launch-plan` (launch). For social teasers, hand off to `social-media-platform-post`. This skill does not dispatch.
Pliki w paczce (2)
  • SKILL.md 3 KB
  • evals.json 1 KB

Wersje

W bazie nie ma innych skilli o nazwie technical-writer-release-notes.

Migawka bazy z 13.11.2026 · wersja paczki 581cb4be6949 (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

  • 100release-notes
    Pisze notatki wydania i changelogi dla użytkowników w formacie Keep a Changelog z sekcjami Added, Changed, Fixed, Deprecated, Removed i Security, z tonem dopasowanym do odbiorcy.
  • 90change-write
    Pisze wpis do changelogu lub notatki wydania dla wersji API: zmiany łamiące, nowe funkcje i poprawki.
  • 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.
  • 100write-a-changelog-entry
    Pisze wpis do changelogu prostym językiem dla użytkowników, grupując zmiany w: dodano, zmieniono, naprawiono, usunięto i bezpieczeństwo.
  • 100changelog
    Pisze notatki do wydania i wpis w CHANGELOG.md na podstawie historii gita od ostatniego tagu.
  • 90changelog-writer
    Czyta historię git i pisze wpis w CHANGELOG dla użytkowników w formacie Keep a Changelog.

Uwagi i zgłoszenia

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