Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

release

/release

Dodaje wydanie do każdego PR: podbija wersję wtyczki, pisze wpisy w changelogu i commituje je na bieżącej gałęzi.

Repozytorium
agent-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
26.10.2026

Ocena i bezpieczeństwo

84/ 100Klasa: dobry
Format9 / 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
4
Skrypty
3
Komentarze HTML
0
Adresy URL w SKILL.md
3
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 sprawdzić przed instalacją
  • 3 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/create-release-pr.sh, scripts/release-info.sh, scripts/release-info_test.sh

Co robi i kiedy

Dodaje wydanie do każdego PR: podbija wersję wtyczki, pisze wpisy w changelogu i commituje je na bieżącej gałęzi.

Wyzwalacze z opisu

releasecut a releasecreate a release PRprepare a releasebump version
Oryginalny opis (EN)

Adds the release that every PR must carry, and runs before creating or pushing any PR. Bumps the plugin version and writes changelog entries: gathers merged PRs since the last tag plus unmerged current-branch changes, decides the semver bump, and commits the release onto the current branch (or opens a release PR from main). Runs non-interactively. Triggers when preparing, pushing, or finalizing a PR, or when the user says "release", "cut a release", "create a release PR", "prepare a release", or "bump version".

Jak działa

  1. Steps
Sekcje z nagłówków SKILL.md, w oryginale · 87 linii, 620 słów
Podgląd SKILL.md
---
description: >-
  Adds the release that every PR must carry, and runs before creating or
  pushing any PR. Bumps the plugin version and writes changelog entries:
  gathers merged PRs since the last tag plus unmerged current-branch changes,
  decides the semver bump, and commits the release onto the current branch (or
  opens a release PR from main). Runs non-interactively. Triggers when
  preparing, pushing, or finalizing a PR, or when the user says "release",
  "cut a release", "create a release PR", "prepare a release", or "bump
  version".
---

Add a release (version bump + changelog) to the current branch before its PR is created or updated. Every PR must include a release.

This skill is **non-interactive**. Decide the version and changelog yourself; do not ask the user to confirm the classification, version, or wording. Only stop and report if a script returns an error.

## Steps

### 1. Gather release info

Run the info script to collect merged PRs and calculate the version:

```bash
bash .claude/skills/release/scripts/release-info.sh 2>&1
```

Capture the JSON output (errors may arrive on stderr, hence `2>&1`). If the error is `already_released`, the branch already carries its release commit (each branch gets exactly one; later commits such as review fixes ship under it). There is nothing to do, so skip the remaining steps and report that. This is not a failure. `stale_release` means another PR already shipped this branch's version; stop and tell the operator to bump the version manually by updating all four version fields (`.claude-plugin/plugin.json`, the `codagent` entry in `.claude-plugin/marketplace.json`, `.codex-plugin/plugin.json`, `.cursor-plugin/plugin.json`) and renaming the branch's `## <version>` heading in `CHANGELOG.md` to match, then rerun this skill. Updating only some of these can make the next run report `already_released` and leave the rest stale. For any other `"error"`, stop and report the message to the user.

### 2. Decide the classification and version

The script's classification comes from conventional commit prefixes, which is only a heuristic. Review it and adjust on your own judgment:
- Internal changes (tooling, CI, repo automation, skills used only by maintainers such as this one) are patch-level even if prefixed with `feat:`.
- User-facing new capabilities in shipped skills are minor.
- Breaking changes to shipped skills' behavior or interfaces are major.

Recompute `new_version` from `current_version` if you change any category (major → `X+1.0.0`, minor → `X.Y+1.0`, otherwise `X.Y.Z+1`). Briefly state the chosen version and classification in your output, then continue without waiting.

### 3. Write changelog descriptions

For each PR in the JSON output, write a one-sentence description that is slightly more informative than the raw PR title. Strip the conventional commit prefix from the title (`feat:`, `fix:`, `chore:`, etc.) and expand it into a sentence that gives enough context to understand the change without clicking through.

If an entry has `"is_branch_commits": true` and `"number": 0`, it represents unmerged commits on the current branch. Read the commit messages (`git log origin/main..HEAD --oneline --no-merges`) and write a description summarizing those changes. Omit the PR link for these entries since they have no PR yet — just use a bullet with the description.

### 4. Format the changelog section

Build the changelog section for the new version. Only include sections that have entries. Sort entries by PR number ascending within each section.

Format:

```
## <new_version>

### Major Changes

- [#<number>](https://github.com/Codagent-AI/agent-skills/pull/<number>) <description>

### Minor Changes

- [#<number>](https://github.com/Codagent-AI/agent-skills/pull/<number>) <description>

### Patch Changes

- [#<number>](https://github.com/Codagent-AI/agent-skills/pull/<number>) <description>
- <description without link> (for branch-commit entries with no PR)
```

### 5. Write the changelog section to a temp file

Write the formatted changelog section (from step 4) to a temporary file:

```bash
TMPFILE=$(mktemp)
cat <<'CHANGELOG_EOF' > "$TMPFILE"
<paste the formatted changelog section here>
CHANGELOG_EOF
echo "$TMPFILE"
```

### 6. Commit the release

Run the release script with the new version and temp file path:

```bash
bash .claude/skills/release/scripts/create-release-pr.sh <new_version> <tmpfile_path>
```

On a feature branch, this commits the release onto the branch and pushes it; if the branch has no PR yet, the calling workflow (e.g. `codagent:push-pr` or `codagent:finalize-pr`) creates it next. On `main`, it creates a `release/v<new_version>` branch and opens a release PR.

### 7. Report

Print the version and the PR URL returned by the script (or note that no PR exists yet).

Clean up the temp file:

```bash
rm -f "$TMPFILE"
```
Pliki w paczce (4)
  • SKILL.md 5 KB
  • scripts/create-release-pr.sh 3 KB
  • scripts/release-info.sh 6 KB
  • scripts/release-info_test.sh 4 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · codagent-ai/agent-skills84MIT
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

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

  • 100version-release
    Podbija wersję, tworzy tag wydania i wypycha tag do repozytorium.
  • 90release-tag
    Wydaje wersję: ustala podbicie SemVer z historii, aktualizuje pliki wersji, odświeża changelog i tworzy tag Git.
  • 100chamoji-release
    Wydaje wersję z historii gita jednym poleceniem: dobiera podbicie semver, dopisuje CHANGELOG i tworzy commit z tagiem.
  • 90qmai-release
    Wydaje stabilną wersję QMAI: aktualizuje metadane i changelog, wypycha main i tworzy adnotowany tag wersji.
  • 100ac-release
    Prowadzi przepływ wydania: branch, changelog, pull request, tag i wydanie na GitHubie.
  • 90bump
    Podbija wersję wtyczki crux-hive, aktualizuje changelog i przygotowuje PR z wydaniem.

Uwagi i zgłoszenia

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