Przejdź do treści
Biblioteka skilli
Programowanie · Pisanie

release-notes

/release-notes

Pisze wpis do notatek wydania dla gałęzi w zmienianym programie hive, desktop lub drive-server, zanim PR zostanie otwarty.

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

Brak sygnałów. Repozytorium zmienione 25.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 wpis do notatek wydania dla gałęzi w zmienianym programie hive, desktop lub drive-server, zanim PR zostanie otwarty.

Oryginalny opis (EN)

Write the release-notes line a branch owes to the changelog of the program it changes -- cmd/hive/releasenotes/changelog/unreleased/ for the hive CLI, cmd/desktop/releasenotes/changelog/unreleased/ for Hive Desktop, cmd/drive-server/releasenotes/changelog/unreleased/ for Hive Drive Server. Use when asked to update the changelog or release notes, or to check whether the work on this branch earns an entry before the PR goes up.

Jak działa

  1. 1. Find what the branch changed
  2. 2. Decide whether it earns a note
  3. 3. Add to an existing fragment, or write a new one
  4. 4. Write it well
  5. 5. Verify
Sekcje z nagłówków SKILL.md, w oryginale · 138 linii, 996 słów
Podgląd SKILL.md
---
name: release-notes
description: Write the release-notes line a branch owes to the changelog of the program it changes -- cmd/hive/releasenotes/changelog/unreleased/ for the hive CLI, cmd/desktop/releasenotes/changelog/unreleased/ for Hive Desktop, cmd/drive-server/releasenotes/changelog/unreleased/ for Hive Drive Server. Use when asked to update the changelog or release notes, or to check whether the work on this branch earns an entry before the PR goes up.
---

# Add a release note

A user-visible change adds a fragment to the changelog of the program it
changes, **in the pull request that earns it**:

| Program | `--product` | Changelog |
| --- | --- | --- |
| hive CLI/TUI (`cmd/hive`) | `cli` | `cmd/hive/releasenotes/changelog/` |
| Hive Desktop (`cmd/desktop`) | `desktop` | `cmd/desktop/releasenotes/changelog/` |
| Hive Drive Server (`cmd/drive-server`) | `drive-server` | `cmd/drive-server/releasenotes/changelog/` |

Every release ships every program under one version. The desktop embeds its
changelog and shows the fragments as the draft in the app; the CLI's and the drive server's notes ship
on the GitHub release. Either way, what you write here is the product's
changelog, not a note to a future maintainer.

A change to the shared `internal/` packages earns a note in each program
whose users can notice it, and only there. One that changes both programs'
behaviour gets one fragment per program, each written for that program's
users.

One file per change is what keeps concurrent branches from conflicting over the
changelog, so **never collapse two branches' notes into one file and never
create the file by hand** -- `changelog:new` builds the name
(ADR [release-notes-accumulate-as-fragments](../../../docs/decisions/2026-09-12-release-notes-accumulate-as-fragments.md)).

A `changelog/<version>.md` is written by promotion during a release, on `main`,
by `cmd/tools/release`. Writing one on a feature branch is wrong even when the version
looks obvious, and a file naming a prerelease is rejected at parse time.

## 1. Find what the branch changed

```bash
git diff main...HEAD --stat
git log main..HEAD --format='%s%n%n%b'
```

The commit bodies carry the intent, which is most of the line already. For a
PR that is not the checked-out branch, `gh pr diff <number>` and
`gh pr view <number>`.

## 2. Decide whether it earns a note

The test is whether a user could notice without reading the diff.

Earns a note:

- a capability that did not exist -- a view, an overlay, a connector, a source,
  a node type, an MCP tool, a palette scope, a shortcut, a CLI command or flag,
  a TUI keybinding;
- behaviour that changed under someone who was already using it, including a
  default, a keybinding, or where something opens;
- a bug a user could hit, described as the symptom they saw;
- a new `settings.yaml` key or `actions.yml` field they can write, or a new
  key in the CLI's config file.

Earns nothing:

- a refactor with no behaviour change, however large;
- tests, fixtures, mocks, e2e specs;
- CI, mise tasks, lefthook, `cmd/` development tooling;
- `docs/`, ADRs, `AGENTS.md`, agent skills;
- a change to the shared `internal/` packages or a dependency bump that changes
  nothing visible in either program;
- a fix to something that never reached a build a user runs -- if the bug was
  introduced and fixed inside the same draft cycle, correct or delete the
  fragment that described it instead of adding a "Fixed" note beneath it.

## 3. Add to an existing fragment, or write a new one

Read what is already unreleased before writing:

```bash
ls cmd/hive/releasenotes/changelog/unreleased/ cmd/desktop/releasenotes/changelog/unreleased/ cmd/drive-server/releasenotes/changelog/unreleased/
```

**If a fragment already describes the exact surface you touched, edit that
fragment** so the release says what the app now does rather than listing five
days of work. A feature that lands over several PRs is one note. Two branches
editing the same fragment is a real conflict worth resolving by hand; that is
the trade, and it is rare.

Otherwise write a new one:

```bash
mise run changelog:new -- --product desktop --kind added "**A notify terminal node**, so a feed can notify on new items."
```

`--product` is `cli`, `desktop`, or `drive-server`. `--kind` is `added`, `changed`, or
`fixed` -- the section it renders under. For
a note that spans lines, pipe it on stdin instead of quoting it:

```bash
mise run changelog:new -- --product desktop --kind fixed <<'NOTE'
**Refresh now fetches.** The feed's Refresh button and `r` re-read the
database and nothing else, so a source was only ever as fresh as the last
poll tick.
NOTE
```

The command prints the path it wrote. Read it back and edit the body or the
`kind` header if either needs work. The filename is only an ordering key, so
it does not have to match what the note ends up saying -- leave it alone.

## 4. Write it well

This is product copy a user reads: inside the app for the desktop, on the
GitHub release for the CLI. **The Simplified Technical
English rule in `CONTRIBUTING.md` applies to commit and PR text, not here** --
write these the way the committed entries in `changelog/*.md` are written.

- one fragment is one bullet: open with the thing in bold, then say what it
  does and where it is:
  `**A notify terminal node**, so a feed can notify on new items.`
- present tense, addressed to the user, describing the app rather than the
  work: "the palette knows where you are", never "we added" or "this PR";
- name the surface a user can find (`Settings ▸ Terminal`, the command palette,
  the Code view's session tree, `hive hc next`, the TUI's tasks view) and
  config keys as they are written (`profiles.order` in `settings.yaml`);
- for a `changed` note, say what a user has to do differently, and for a
  `fixed` note, describe the symptom, not the cause;
- mark an unfinished area `(experimental)` the way Terminal mode and Chats are;
- never name a Go package, a Vue component, an ADR, an issue, or a PR number.

Do not write a release summary. The draft has no `summary`: it describes a
whole release, which no single change can write, so promotion writes it.

## 5. Verify

```bash
go test ./cmd/hive/releasenotes/... ./cmd/desktop/releasenotes/... ./cmd/drive-server/releasenotes/...
```

Each program's `TestChangelogParses` reads its embedded files, so a broken header, an unknown kind, a name the tool did not build, or
an empty body fails there rather than at release time. It runs inside
`mise run check`, which the pre-push hook already runs.

Wersje

RepozytoriumWynikLicencja
Ta strona · colonyops/hive100MIT
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 10cfeb30207d (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 lub aktualizuje CHANGELOG.md dla nowego wydania, sekcji Unreleased albo na podstawie historii gita i diffa.
  • 100release
    Wydaje jednocześnie CLI hive i aplikację Hive Desktop pod wspólną wersją.
  • 90changelog
    Uzupełnia sekcję Unreleased w CHANGELOG, dodając jedną linię na commit z linkami do commitów i PR.
  • 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.
  • 100changelog-entry
    Dodaje wpis do CHANGELOG.md w formacie Keep a Changelog, w odpowiedniej sekcji Unreleased, dla opisanej zmiany.

Uwagi i zgłoszenia

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