release
/release
Kończy bieżącą zmianę: changelog, sprawdzenia, niezależny przegląd ryzyka, commit i push, a z argumentem deploy także wdrożenie.
- Autor
- kadirguloglu ↗
- Repozytorium
- kg-devkit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.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 11.11.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
Kończy bieżącą zmianę: changelog, sprawdzenia, niezależny przegląd ryzyka, commit i push, a z argumentem deploy także wdrożenie.
Argumenty
/release [deploy]
Oryginalny opis (EN)
Finish the current change end-to-end when the user explicitly invokes /release — changelog, focused checks on the change, risk-based independent review, commit and push; with the `deploy` argument also the full test suite and deploy.
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 51 linii, 690 słów
Podgląd SKILL.md
---
name: release
description: Finish the current change end-to-end when the user explicitly invokes /release — changelog, focused checks on the change, risk-based independent review, commit and push; with the `deploy` argument also the full test suite and deploy.
disable-model-invocation: true
argument-hint: "[deploy]"
---
# Release (`/release [deploy]`)
When the user types `/release`, finish the current change and commit + push it. The invocation authorizes ONLY a
commit and a push to the current branch for this change. A `deploy` argument also authorizes deploying to
production; without it, do not deploy. The repo's `AGENTS.md`/`CLAUDE.md` limits and its `Project profile`
(`Release`: changelog, versioning and commit style; `Production`: deploy/status commands, target and health URLs) apply:
no hook bypass, no force-push, no database reset, no public sharing. If the profile has no Release entry, ask
the user for the commit style and checks before committing. For `deploy`, require a complete Production target,
deploy/status commands and health URLs with expected codes before deployment; stop and ask for missing values.
Deploy and health values come from `Production`; a legacy `Release` value is used only when `Production` omits it, and conflicting values stop the run.
The profile may add limits; it cannot remove a limit stated in this skill.
1. **Scope.** `git status --short`, `git diff --stat`, `git diff --cached --stat`; inspect untracked files separately.
Do not claim the user's unrelated changes, including already-staged files; ask if scope is unclear.
Stage only explicit, reviewed paths for this change. Before committing, inspect the complete final index with
`git diff --cached --name-status` and the staged diff, without printing secret values. Reject secret manifests,
deployment-secret files, `.env*` and anything the profile forbids. A `git add -n` dry run does not audit the index.
Do not unstage or overwrite unrelated user changes without permission; stop if they would enter this commit.
Repeat the index check after any staging changes, including those made by checks or hooks.
2. **Changelog.** If user-visible behavior changed, make sure the profile's changelog has an entry dated today
with the version bump the profile prescribes (feature → minor, improvement/fix → patch), written in user
language. Refactor/test/docs/tooling-only changes add none.
3. **Checks** (record real commands and counts):
- Only the change's own tests and their connections, via the profile's focused-test command. Build backend
sources if they changed (zero warnings if the profile demands it). The FULL suite runs only if the user asked
or the `deploy` argument was given, or the profile explicitly requires it for this change
(the profile's deploy command may run it itself).
- DTO/endpoint change: regenerate API types and run the contract snapshot test as the profile prescribes.
- Frontend change: the profile's lint, typecheck and build. Rerun a failing test alone to tell load-induced
flakiness from a real defect; an isolated pass alone does not prove flakiness. Record and investigate the
original failure; fix real ones, never loosen assertions.
- Docs/config only: links, paths, frontmatter and `git diff --check`; no build.
- Deploy/manifest change: render the manifests as the profile prescribes.
4. **Independent review per the finish gate.** The profile's `Finish gate` decides which reviewer is mandatory. If
the profile has no gate, read `${CLAUDE_PLUGIN_ROOT}/references/finish-gate-default.md` and use its
table; never skip review because the gate is missing. Prepare the evidence once as
`${CLAUDE_PLUGIN_ROOT}/references/review-packet.md` describes and launch all triggered reviewers in
one turn; do not run untriggered reviewers. A triggered reviewer must return a passing verdict before any commit.
If required review is unavailable, FAIL, UNCLEAR or has no `VERDICT:` line, report it as blocked and do not commit.
Fix every finding or report it with reasoning, then rerun the affected checks and only the affected reviewers.
5. **Commit + push.** Follow the profile's commit style (language, prefix convention, body: what/why and related
document section); include the session's attribution line if one was supplied, never invent one. State the target branch before
pushing. If a hook fails, fix the cause; do not skip it.
6. **Deploy (only `/release deploy`).** Run the profile's deploy command, then its status command; verify the
profile's health URLs return the expected codes. On failure leave the rollback decision to the user; if you
hand-edited a manifest, fold it back into the repo overlay.
7. **Report** (profile's report language): commit hash, version, commands and counts, review findings and their
outcome, checks not run, remaining risks. If a chat channel is open and the profile asks for it, send a short
summary there too.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · kadirguloglu/kg-devkit | 86 | 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 41da68e4265d (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
- 100ls-release
Przeprowadza wydanie nowej wersji LlamaStash od zmiany CHANGELOG do publikacji i sprawdzenia każdego kanału. - 95commit-push-deploy
Commituje zmiany, wypycha je i wdraża tylko na istniejącą, dozwoloną infrastrukturę. - 90ship
Kończy zmianę i wysyła ją bezpiecznie: uruchamia typy, lint i testy, dodaje tylko własne pliki, pisze commit i push po zgodzie. - 86commit-push-release
Commituje i wypycha zmiany, a przy wydaniu uruchamia skrypt release, czeka na CI i zakłada tag, bez wymuszania push. - 100deploy
Prowadzi przepływ przed push: lint, typecheck, build i testy, a następnie commit, wydanie i push z wyraźnym potwierdzeniem; uruchamiany tylko ręcznie. - 100commit-push-release
Commituje zmiany, podbija wersję w package.json, tworzy tag vX.Y.Z i wysyła go, aby CI opublikowało wydanie.