release
/release
Wydaje wtyczkę project-with-reflect dla opiekuna repozytorium: podbija wersję, changelog, tag i GitHub release.
- Autor
- initialneil ↗
- Repozytorium
- project-with-reflect ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wydaje wtyczkę project-with-reflect dla opiekuna repozytorium: podbija wersję, changelog, tag i GitHub release.
Argumenty
/release [patch | minor | major | X.Y.Z] [\"note\"]
Oryginalny opis (EN)
Ship a new version of THIS repo's project-with-reflect plugin in one step: publish (bump + changelog + commit + tag + push + GitHub release via scripts/publish.sh) then refresh the local install. Use when the user types /release in the project-with-reflect repo, or asks to release / publish / cut a new version. Maintainer-only — this project skill is NOT shipped to plugin consumers.
Jak działa
- Usage
- Steps
- Guardrails
Podgląd SKILL.md
--- name: release description: >- Ship a new version of THIS repo's project-with-reflect plugin in one step: publish (bump + changelog + commit + tag + push + GitHub release via scripts/publish.sh) then refresh the local install. Use when the user types /release in the project-with-reflect repo, or asks to release / publish / cut a new version. Maintainer-only — this project skill is NOT shipped to plugin consumers. argument-hint: "[patch | minor | major | X.Y.Z] [\"note\"]" --- # /release — ship a new project-with-reflect version One command for the whole pipeline: **publish → refresh the local install**, so the loop is `edit the skill → /release`. ## Usage ``` /release [patch|minor|major | X.Y.Z] ["one-line changelog note"] ``` Version-bump map (this project's convention): - **major** — a user-facing big / breaking change → bumps the **first** number. - **minor** — a **major fix** → bumps the **middle** number. - **patch** — a **minor fix** → bumps the **last** number. **(default)** - An explicit `X.Y.Z` is also accepted. The **note** becomes the CHANGELOG entry. If omitted, summarize what changed in the plugin since the last tag in one line — don't invent a generic message. ## Steps 1. **Locate the repo.** Work from the repo root (the dir with `.claude-plugin/plugin.json` and `scripts/publish.sh`). If the CWD isn't it, `cd` to `~/Playground/vibe_coding/project-with-reflect`. 2. **Preflight (report, don't nag).** `git status` to show what's being released; confirm you're on `main`. Echo one line: `releasing vCUR → vNEXT — <note>`. The user typing `/release` IS the go-ahead — don't prompt again. 3. **Publish.** Run `scripts/publish.sh <bump-or-version> "<note>"`. It bumps the version in both manifests, prepends the CHANGELOG, commits, tags `v<version>`, pushes, and (if `gh` is present) cuts a GitHub release. 4. **Refresh this machine's install.** If installed via the marketplace, run `claude plugin marketplace update project-with-reflect`. If installed via the user-scope symlink (`~/.claude/skills/project-with-reflect` → this repo), it's already live — nothing to do. 5. **Report.** Print the new version + tag, and remind that other users update with `/plugin update project-with-reflect`. ## Guardrails - `/release` **pushes a public tag.** Run it only when the user invoked `/release` — never speculatively, never as a side effect of another task. - If `scripts/publish.sh` fails (push rejected, tag exists, bad version), **STOP and report the exact failure.** Don't force-push or re-tag without asking. - A release is for **plugin/skill changes only** — README / tooling / CI edits are a plain `git commit` + `git push`, not `/release`. - Don't edit skill *content* here — `/release` ships what's already committed.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · initialneil/project-with-reflect | 100 | MIT |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 96fe27d04d7e (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-plugin
Wydaje to repozytorium: dobiera wzrost wersji ze zmian, aktualizuje changelog i stopkę canvasu, taguje i publikuje wydanie na GitHub. - 100ship-release
Wydaje nową wersję projektu: podbija manifesty, aktualizuje CHANGELOG, taguje, tworzy release na GitHub i publikuje na npm. - 100version-release
Podbija wersję, tworzy tag wydania i wypycha tag do repozytorium. - 90ship
Wydaje bieżący stan projektu: sprawdza gotowość, podbija wersję i tag, dopisuje wpis do changelogu, wdraża i przygotowuje szkic ogłoszenia. - 100nvidia-nemoclaw-maintainer-cut-release-tag
Wydaje nową wersję semver: podbija numery wersji skryptem bump-version.ts, otwiera pull request wydania, a po scaleniu taguje main i wypycha tag. - 100ls-release
Przeprowadza wydanie nowej wersji LlamaStash od zmiany CHANGELOG do publikacji i sprawdzenia każdego kanału.