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

publish-release

/publish-release

Prowadzi wydanie zmian we wtyczkach dla użytkowników marketplace: ocenia, czy zmiana jest widoczna dla instalatora, podbija wersję manifestu, waliduje, wypycha i odświeża wtyczkę w Codex i Claude Code.

Repozytorium
claude-plugins ↗
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

Prowadzi wydanie zmian we wtyczkach dla użytkowników marketplace: ocenia, czy zmiana jest widoczna dla instalatora, podbija wersję manifestu, waliduje, wypycha i odświeża wtyczkę w Codex i Claude Code.

Oryginalny opis (EN)

Release runbook for this repo — invoke when a plugin change-set is ready to ship to marketplace users, or the user says ship/publish/release a plugin. Judge first whether the change is installer-visible and the change-set is complete; then bump the affected plugin's manifest version once, validate, push/merge, and refresh the plugin in both Codex and Claude Code.

Jak działa

  1. When to run — and when not to
  2. The one non-negotiable
  3. Steps
  4. If a harness-specific runbook is ever needed
Sekcje z nagłówków SKILL.md, w oryginale · 92 linii, 655 słów
Podgląd SKILL.md
---
name: publish-release
description: Release runbook for this repo — invoke when a plugin change-set is ready to ship to marketplace users, or the user says ship/publish/release a plugin. Judge first whether the change is installer-visible and the change-set is complete; then bump the affected plugin's manifest version once, validate, push/merge, and refresh the plugin in both Codex and Claude Code.
---

# Publish a plugin/skill release

Runbook for shipping a plugin change to the people who install these plugins.
Run it — using the judgment below, or on an explicit `/publish-release` — once a
change-set is complete and ready to release. It is the checklist; the
authoritative step-by-step procedure lives in
[`docs/release.md`](../../../docs/release.md), which this skill
points into rather than duplicating.

A change that reaches only your local working tree is not released. "Released"
means the version is bumped, tests pass, and the change is merged to the ref
marketplace users install from.

## When to run — and when not to

Run it when **both** are true:

- The change is **installer-visible**: a plugin's skills, commands, hooks,
  scripts, or manifest changed in a way someone who installs the plugin would
  notice.
- The **change-set is complete** — the feature or fix is done, not mid-flight.
  Commit and iterate freely while you work; a release is the moment the whole
  set is ready, not each step along the way.

The user saying ship / publish / release / push a plugin is an explicit signal
that both are true.

Do **not** run for:

- Whitespace-, typo-, or comment-only commits, unless the user asks.
- Changes that never reach installers: repo-root `AGENTS.md` / `README.md`,
  `docs/`, maintainer `scripts/`, `tests/`, CI config, or a repo-local
  `.claude/` skill like this one — none of these is a distributed plugin.
- Local experiments not yet merged.

When it is genuinely ambiguous whether a change is installer-visible, remember a
release is outward-facing and hard to walk back — confirm before shipping rather
than bumping on a hunch.

## The one non-negotiable

When you **do** release, the affected plugin's manifest version **must** be
bumped as part of that release. Plugin versions are release identifiers **and**
Codex cache keys — an installer-visible change that ships with no version bump
defeats the cache transition and leaves users on stale content. Semver: patch
for fixes, minor for non-breaking additions, major for breaking changes.

**One release, one bump.** Bump once for the whole change-set, at release
time — not on every interim fix or commit within a session. Several fixes
shipping together get a single version delta, not one bump per commit. If more
than one plugin changed, bump each affected plugin's manifest independently and
release each; never bump a manifest for a plugin that did not actually change.

## Steps

Follow `docs/release.md` for the full detail of each; the short form:

1. **Identify what changed and which surfaces publish it.** Which plugin
   directory changed? Is it offered through the Claude marketplace
   (`.claude-plugin/marketplace.json`), the Codex-native catalog
   (`.agents/plugins/marketplace.json`), or both? (release.md §1)
2. **Bump the manifest version** in the affected plugin's
   `.claude-plugin/plugin.json` (or `.codex-plugin/plugin.json` for a
   Codex-native-only plugin). Do not bump manifests the plugin does not
   actually publish. (release.md §1–2)
3. **Validate.** If a skill changed, run `validate-dual-harness-skill` against
   it and do representative Claude Code + Codex probes when behavior changed.
   Then run the repo gate and read its summary, not just the exit code:
   ```bash
   bash tests/run-all.sh
   ```
   (release.md §2)
3b. **Compound.** Run the `compounding-preflight` skill over the change-set: fix
   any violations of [`docs/compounding.md`](../../../docs/compounding.md), add
   the entry the change-set taught (per the doc's write gate), and prune entries
   it made obsolete. A release that learned nothing states that in one line.
4. **Commit, push, and merge** the complete change to the ref installers use.
   (release.md §2)
5. **Refresh Codex** and confirm the new version materialized in the cache.
   (release.md §3)
6. **Verify Claude Code** — update the marketplace, install/update the plugin,
   start a new session, and run a `/<plugin>:<skill>` probe. Codex-native-only
   plugins have no Claude step. (release.md §4)

## If a harness-specific runbook is ever needed

Today `docs/release.md` is the shared runbook. If either harness grows a
specialized release path, add a harness-specific companion under `docs/claude/`
or `docs/codex/` and link it from the shared guide—keep this skill as the single
manual entry point that fans out to both.

Wersje

RepozytoriumWynikLicencja
Ta strona · jtsternberg/claude-plugins100MIT
organizzolini/codebase90MIT

Migawka bazy z 13.11.2026 · wersja paczki f98c1fdf51f5 (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
    Wydaje wtyczkę z tego repozytorium: podbija wersję, aktualizuje changelog, waliduje, publikuje release na GitHub i odświeża wersję lokalnie.
  • 100release
    Wydaje nową wersję skilla coding-by-contract: podbija numer, pisze changelog, taguje i odświeża lokalną instalację.
  • 100release
    Wydaje nową wersję skilla grounding-rules: podbija numer, pisze changelog, taguje i odświeża lokalną instalację.
  • 100release
    Wydaje wtyczkę project-with-reflect dla opiekuna repozytorium: podbija wersję, changelog, tag i GitHub release.
  • 100release-plugin
    Wydaje aktualizację wtyczki Claude Code: wykrywa wtyczkę, ustala podbicie, aktualizuje plugin.json i CHANGELOG, a potem wypycha zmiany.
  • 100release-plugin
    Podbija wersję wtyczki Claude Code dla squads: zmienia numer, taguje i tworzy release na GitHubie.

Uwagi i zgłoszenia

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